Add import_to_main flag for Main module package name conflicts reso…
#281
krynjuci.yml
on: push
ci_started
0s
docs
1m 32s
Matrix: test
Annotations
24 errors and 5 notices
|
test (1.6, x64, macOS-latest, true)
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, x64, macOS-latest, true)
Encountered error: Could not find aarch64/1.6.7 binaries
|
|
test (1.9, x64, macOS-latest, false)
Process completed with exit code 1.
|
|
test (1.9, x64, macOS-latest, true)
Process completed with exit code 1.
|
|
test (1.10, x64, macOS-latest, false)
Process completed with exit code 1.
|
|
test (1.10, x64, macOS-latest, true)
Process completed with exit code 1.
|
|
test (1.9, x64, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.9, x86, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (1.9, x86, ubuntu-latest, false)
Process completed with exit code 1.
|
|
test (1.9, x64, ubuntu-latest, false)
Process completed with exit code 1.
|
|
test (nightly, x64, macOS-latest, true)
Process completed with exit code 1.
|
|
test (nightly, x64, macOS-latest, false)
Process completed with exit code 1.
|
|
test (1.9, x64, windows-latest, true)
Process completed with exit code 1.
|
|
test (1.9, x64, windows-latest, false)
Process completed with exit code 1.
|
|
test (1.9, x86, windows-latest, false)
Process completed with exit code 1.
|
|
test (1.9, x86, windows-latest, true)
Process completed with exit code 1.
|
|
test (nightly, x64, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (nightly, x64, ubuntu-latest, false)
Process completed with exit code 1.
|
|
test (nightly, x86, ubuntu-latest, true)
Process completed with exit code 1.
|
|
test (nightly, x86, ubuntu-latest, false)
Process completed with exit code 1.
|
|
test (nightly, x64, windows-latest, true)
Process completed with exit code 1.
|
|
test (nightly, x64, windows-latest, false)
Process completed with exit code 1.
|
|
test (nightly, x86, windows-latest, true)
Process completed with exit code 1.
|
|
test (nightly, x86, windows-latest, false)
Process completed with exit code 1.
|
|
test (1.6, x64, macOS-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, x86, 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, x64, 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, x64, 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, x86, 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.
|