Leipzig workshop #17682
Triggered via pull request
November 28, 2024 12:19
Status
Failure
Total duration
1h 1m 55s
Artifacts
–
Annotations
6 errors, 4 warnings, and 2 notices
test (1.10, short, macOS, RPTU)
Process completed with exit code 1.
|
test (1.11-nightly, short, ubuntu-latest)
Process completed with exit code 1.
|
test (nightly, short, ubuntu-latest)
Process completed with exit code 1.
|
test (1.10, short, ubuntu-latest)
Process completed with exit code 1.
|
test (1.10, short, ubuntu-latest, depwarn=error)
Process completed with exit code 1.
|
test (1.6, short, ubuntu-latest)
Process completed with exit code 1.
|
doctest (1.10, macOS, RPTU)
Codecov: Error importing gpg key: Command failed: gpg --logger-fd 1 --no-default-keyring --import /Users/aaruni/Desktop/oscar-runners/runner-3/_work/_actions/codecov/codecov-action/v4/dist/pgp_keys.asc
|
doctest (1.10, macOS, RPTU)
Codecov: Error verifying gpg signature: Command failed: gpg --logger-fd 1 --verify /Users/aaruni/Desktop/oscar-runners/runner-3/_work/_actions/codecov/codecov-action/v4/dist/codecov.SHA256SUM.sig /Users/aaruni/Desktop/oscar-runners/runner-3/_work/_actions/codecov/codecov-action/v4/dist/codecov.SHA256SUM
|
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-1/_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-1/_work/_actions/codecov/codecov-action/v4/dist/codecov.SHA256SUM.sig /Users/aaruni/Desktop/oscar-runners/runner-1/_work/_actions/codecov/codecov-action/v4/dist/codecov.SHA256SUM
|
test (1.6, short, 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, long, 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.
|