Move the build-mylib test into the regular test suite (and get rid of the separate build-mylib CI job)
#486
Triggered via pull request
November 25, 2024 04:45
DilumAluthge
Status
Failure
Total duration
1h 21m 16s
Artifacts
–
Annotations
11 errors and 3 notices
|
test (1.10, 64, macos-14, true)
Process completed with exit code 1.
|
|
test (1.6, 64, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.6, 64, macos-13, true)
Process completed with exit code 1.
|
|
test (1.11, 64, macos-14, true)
Process completed with exit code 1.
|
|
test (1.10, 64, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.10, 32, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.10, 64, macos-13, true)
Process completed with exit code 1.
|
|
test (1.11, 64, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.11, 32, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.11, 64, macos-13, true)
Process completed with exit code 1.
|
|
finalize
Process completed with exit code 1.
|
|
test (1.6, 64, ubuntu-latest, true)
[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, 64, macos-13, true)
[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, 64, windows-latest, true)
[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.
|