Skip to content

Update rand_core requirement from 0.6 to 0.9 #318

Update rand_core requirement from 0.6 to 0.9

Update rand_core requirement from 0.6 to 0.9 #318

Triggered via push January 28, 2025 05:49
Status Failure
Total duration 36s
Artifacts

main.yml

on: push
test on nightly
28s
test on nightly
Matrix: build-nostd
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 8 warnings
Build target wasm32-wasi
Process completed with exit code 1.
Build target thumbv7em-none-eabihf
The job was canceled because "wasm32-wasi" failed.
Build target thumbv7em-none-eabihf
Process completed with exit code 1.
test on nightly: src/batch.rs#L125
the trait bound `R: rand_core::RngCore` is not satisfied
test on nightly: src/batch.rs#L125
the trait bound `R: rand_core::CryptoRng` is not satisfied
test on nightly: src/signing_key.rs#L75
the trait bound `R: rand_core::RngCore` is not satisfied
test on nightly: src/signing_key.rs#L75
the trait bound `R: rand_core::CryptoRng` is not satisfied
test on nightly: src/signing_key.rs#L82
the trait bound `R: rand_core::RngCore` is not satisfied
test on nightly: src/signing_key.rs#L82
the trait bound `R: rand_core::CryptoRng` is not satisfied
test on nightly
could not compile `redjubjub` (lib) due to 6 previous errors
test on nightly
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
test on nightly
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
test on nightly
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/rusty-fork/0.3.0/download` (151.101.46.137), got 502
test on nightly
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/proc-macro2/1.0.93/download` (151.101.46.137), got 502
test on nightly
spurious network error (3 tries remaining): failed to get successful HTTP response from `https://static.crates.io/crates/bitvec/1.0.1/download` (151.101.46.137), got 502
test on nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
test on nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
test on nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
test on nightly
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/