Skip to content

CI

CI #1826

Triggered via schedule October 27, 2024 02:56
Status Failure
Total duration 4m 0s
Artifacts

CI.yml

on: schedule
Weakdeps
27s
Weakdeps
Benchmarks
3m 25s
Benchmarks
Documentation - DocTests
42s
Documentation - DocTests
Documentation - Deploy
59s
Documentation - Deploy
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 4 notices
Julia 1 - macos-14 - aarch64
Process completed with exit code 1.
Julia 1.6 - ubuntu-latest - x64
Process completed with exit code 1.
Julia nightly - macos-14 - aarch64
Process completed with exit code 1.
Julia 1.6 - ubuntu-latest - x86
Process completed with exit code 1.
Julia 1 - ubuntu-latest - x64
Process completed with exit code 1.
Julia 1 - ubuntu-latest - x86
Process completed with exit code 1.
Julia nightly - ubuntu-latest - x64
Process completed with exit code 1.
Julia nightly - ubuntu-latest - x86
Process completed with exit code 1.
Julia 1 - windows-latest - x64
Process completed with exit code 1.
Julia 1.6 - macos-13 - x64
Process completed with exit code 1.
Julia nightly - windows-latest - x64
Process completed with exit code 1.
Weakdeps
[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.
Julia 1.6 - ubuntu-latest - x64
[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.
Julia 1.6 - ubuntu-latest - x86
[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.
Julia 1.6 - macos-13 - x64
[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.