Move the build-mylib test into the regular test suite (and get rid of the separate build-mylib CI job)
#430
Triggered via pull request
October 31, 2024 18:59
DilumAluthge
Status
Failure
Total duration
6h 16m 9s
Artifacts
–
Annotations
4 errors, 2 warnings, and 5 notices
|
test (1.6, 32, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.11, 64, macos-13, true)
The job running on runner GitHub Actions 47 has exceeded the maximum execution time of 90 minutes.
|
|
test (1.11, 64, macos-13, false)
The job running on runner GitHub Actions 9 has exceeded the maximum execution time of 90 minutes.
|
|
finalize
Process completed with exit code 1.
|
|
test (1.10, 64, macos-14, true)
Failed to download action 'https://api.github.com/repos/dcarbone/install-jq-action/tarball/8867ddb4788346d7c22b72ea2e2ffe4d514c7bcb'. Error: Operation timed out (codeload.github.com:443)
|
|
test (1.10, 64, macos-14, true)
Back off 20.853 seconds before retry.
|
|
test (1.6, 32, 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, 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, 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.
|
|
test (1.6, 32, 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.
|
|
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.
|