Skip to content

Use some unsave operators #613

Use some unsave operators

Use some unsave operators #613

Triggered via pull request January 16, 2025 16:04
Status Failure
Total duration 15m 25s
Artifacts

CI.yml

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

Annotations

11 errors, 1 warning, and 3 notices
test (1.11, stable, ubuntu-latest)
Process completed with exit code 1.
test (1.10, stable, ubuntu-latest)
Process completed with exit code 1.
test (1.10, 1.1, ubuntu-latest)
Process completed with exit code 1.
test (1.11, 1.1, ubuntu-latest)
Process completed with exit code 1.
test (1.6, 1.1, ubuntu-latest)
Process completed with exit code 1.
test (1.11, devel, ubuntu-latest)
Process completed with exit code 1.
test (1.6, stable, ubuntu-latest)
Process completed with exit code 1.
test (1.10, devel, ubuntu-latest)
Process completed with exit code 1.
test (1.6, devel, ubuntu-latest)
Process completed with exit code 1.
test (nightly, stable, ubuntu-latest)
Process completed with exit code 1.
test (nightly, devel, ubuntu-latest)
Process completed with exit code 1.
Documentation
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test (1.6, 1.1, 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, stable, 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, devel, 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.