Skip to content

Improve @perm macro #18362

Improve @perm macro

Improve @perm macro #18362

Triggered via pull request January 22, 2025 18:14
Status Failure
Total duration 2h 37m 42s
Artifacts

CI.yml

on: pull_request
extra-long-test
0s
extra-long-test
Matrix: doctest
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

12 errors, 2 warnings, and 2 notices
test (1.10, short, macOS, RPTU)
Process completed with exit code 1.
test (1.6, short, Linux)
Process completed with exit code 1.
test (1.10, short, Linux)
Process completed with exit code 1.
test (1.10, short, Linux, RPTU, high-memory, depwarn=error)
Process completed with exit code 1.
doctest (1.10, macOS, RPTU)
Process completed with exit code 1.
test (1.11, short, Linux)
Process completed with exit code 1.
doctest (1.11, Linux, RPTU, normal-memory)
Process completed with exit code 1.
doctest (nightly, Linux, RPTU, normal-memory)
Process completed with exit code 1.
doctest (1.10, Linux, RPTU, normal-memory, depwarn=error)
Process completed with exit code 1.
doctest (1.10, Linux, RPTU, normal-memory)
Process completed with exit code 1.
test (nightly, book, Linux, RPTU, normal-memory)
Process completed with exit code 1.
test (nightly, short, Linux)
The job running on runner RPTU-Linux-12 has exceeded the maximum execution time of 150 minutes.
test (1.10, long, macOS, RPTU)
Codecov: Error importing gpg key: Command failed: gpg --logger-fd 1 --no-default-keyring --import /Users/aaruni/Desktop/oscar-runners/runner-2/_work/_actions/codecov/codecov-action/v4/dist/pgp_keys.asc
test (1.10, long, macOS, RPTU)
Codecov: Error verifying gpg signature: Command failed: gpg --logger-fd 1 --verify /Users/aaruni/Desktop/oscar-runners/runner-2/_work/_actions/codecov/codecov-action/v4/dist/codecov.SHA256SUM.sig /Users/aaruni/Desktop/oscar-runners/runner-2/_work/_actions/codecov/codecov-action/v4/dist/codecov.SHA256SUM
test (1.6, short, Linux)
[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, long, Linux)
[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.