Skip to content

large_nightly

large_nightly #980

Triggered via schedule September 14, 2024 10:01
Status Failure
Total duration 28m 50s
Artifacts

CI_large_nightly.yml

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

Annotations

10 errors and 9 notices
test (1.6, 3.10, macos-latest)
It looks like you are trying to install Julia 1.6 or 1.7 on the "macos-latest" runners. "macos-latest" now resolves to "macos-14", which run on Apple Silicon (aarch64) macOS machines. Unfortunately, Julia 1.6 and 1.7 do not have native binaries available for Apple Silicon macOS. Therefore, it is not possible to install Julia with the current constraints. For instructions on how to fix this error, please see the following Discourse post: https://discourse.julialang.org/t/how-to-fix-github-actions-ci-failures-with-julia-1-6-or-1-7-on-macos-latest-and-macos-14/117019
test (1.6, 3.10, macos-latest)
Encountered error: Could not find aarch64/1.6.7 binaries
test (1.6, 3.12, macos-latest)
It looks like you are trying to install Julia 1.6 or 1.7 on the "macos-latest" runners. "macos-latest" now resolves to "macos-14", which run on Apple Silicon (aarch64) macOS machines. Unfortunately, Julia 1.6 and 1.7 do not have native binaries available for Apple Silicon macOS. Therefore, it is not possible to install Julia with the current constraints. For instructions on how to fix this error, please see the following Discourse post: https://discourse.julialang.org/t/how-to-fix-github-actions-ci-failures-with-julia-1-6-or-1-7-on-macos-latest-and-macos-14/117019
test (1.6, 3.12, macos-latest)
Encountered error: Could not find aarch64/1.6.7 binaries
test (1.6, 3.8, macos-latest)
It looks like you are trying to install Julia 1.6 or 1.7 on the "macos-latest" runners. "macos-latest" now resolves to "macos-14", which run on Apple Silicon (aarch64) macOS machines. Unfortunately, Julia 1.6 and 1.7 do not have native binaries available for Apple Silicon macOS. Therefore, it is not possible to install Julia with the current constraints. For instructions on how to fix this error, please see the following Discourse post: https://discourse.julialang.org/t/how-to-fix-github-actions-ci-failures-with-julia-1-6-or-1-7-on-macos-latest-and-macos-14/117019
test (1.6, 3.8, macos-latest)
Encountered error: Could not find aarch64/1.6.7 binaries
test (1.10, 3.8, macos-latest)
[notice] A new release of pip is available: 21.1.1 -> 24.2 [notice] To update, run: python3.8 -m pip install --upgrade pip
test (1.8, 3.8, macos-latest)
[notice] A new release of pip is available: 21.1.1 -> 24.2 [notice] To update, run: python3.8 -m pip install --upgrade pip
test (1.6, 3.10, windows-latest)
Process completed with exit code 139.
test (1.6, 3.8, windows-latest)
Process completed with exit code 139.
test (1.6, 3.10, macos-latest)
[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, 3.12, macos-latest)
[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, 3.8, macos-latest)
[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, 3.10, ubuntu-latest)
[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, 3.8, ubuntu-latest)
[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, 3.12, ubuntu-latest)
[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, 3.10, windows-latest)
[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, 3.8, windows-latest)
[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, 3.12, windows-latest)
[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.