Skip to content
Unit test

Unit test #697

Sign in to view logs

Unit test

Unit test #697

Triggered via create August 18, 2024 18:06
@jishnubjishnub
⁠ 2f1e8ad
Status Failure
Total duration 11m 53s
Artifacts –

UnitTest.yml

on: create
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

3 errors, 3 warnings, and 3 notices
test (nightly, ubuntu-latest, x64)
Process completed with exit code 1.
test (nightly, macOS-latest, x64)
Process completed with exit code 1.
test (nightly, windows-latest, x64)
Process completed with exit code 1.
test (1.0, ubuntu-latest, x64)
The Pkg.test bounds checking behavior cannot be changed before Julia 1.6. VERSION=1.0.5, julia_args=["--check-bounds=yes", "--compiled-modules=yes"]
test (1.0, macOS-latest, x64)
The Pkg.test bounds checking behavior cannot be changed before Julia 1.6. VERSION=1.0.5, julia_args=["--check-bounds=yes", "--compiled-modules=yes"]
test (1.0, windows-latest, x64)
The Pkg.test bounds checking behavior cannot be changed before Julia 1.6. VERSION=1.0.5, julia_args=["--check-bounds=yes", "--compiled-modules=yes"]
test (1.6, ubuntu-latest, x64)
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.
test (1.6, macOS-latest, x64)
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.
test (1.6, windows-latest, x64)
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.