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

Encountered error: Could not find aarch64/1.6.7 binaries

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

Encountered error: Could not find aarch64/1.6.7 binaries

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

Encountered error: Could not find aarch64/1.6.7 binaries

[notice] A new release of pip is available: 21.1.1 -> 24.2 [notice] To update, run: python3.8 -m pip install --upgrade pip

Process completed with exit code 139.

[notice] A new release of pip is available: 21.1.1 -> 24.2 [notice] To update, run: python3.8 -m pip install --upgrade pip

Process completed with exit code 139.

Process completed with exit code 139.

The job running on runner GitHub Actions 19 has exceeded the maximum execution time of 60 minutes.

The operation was canceled.

[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.

[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.

[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.

[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.

[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.

[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.

[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.

[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.