Dec 05 10:57:20.733 INFO checking libsecp256k1-rs-0.2.4 against try#1df97983eb2057dc6a8f7eb364e263b51ae23230 for pr-56481 Dec 05 10:57:20.733 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56481/worker-3/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-56481/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +1df97983eb2057dc6a8f7eb364e263b51ae23230-alt check --frozen --all --all-targets" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Dec 05 10:57:21.182 INFO [stdout] 3b2c14af4b26325ca8b4d057c05741e17b1e0806c74dd5ef4dc7f4e9a2f3dd90 Dec 05 10:57:21.184 INFO running `"docker" "start" "-a" "3b2c14af4b26325ca8b4d057c05741e17b1e0806c74dd5ef4dc7f4e9a2f3dd90"` Dec 05 10:57:22.525 INFO [stderr] usermod: no changes Dec 05 10:57:22.662 INFO [stderr] Compiling secp256k1-test v0.7.2 Dec 05 10:57:22.663 INFO [stderr] Checking crypto-mac v0.4.0 Dec 05 10:57:23.587 INFO [stderr] Checking hmac v0.4.2 Dec 05 10:57:24.555 INFO [stderr] Checking hmac-drbg v0.1.2 Dec 05 10:57:25.896 INFO [stderr] Checking libsecp256k1-rs v0.2.4 (/source) Dec 05 10:57:44.183 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 05 10:57:44.183 INFO [stderr] --> src/secp256k1/keys.rs:157:9 Dec 05 10:57:44.183 INFO [stderr] | Dec 05 10:57:44.183 INFO [stderr] 157 | write!(f, "{}", self.to_hex(true)); Dec 05 10:57:44.183 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 05 10:57:44.183 INFO [stderr] | Dec 05 10:57:44.183 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 05 10:57:44.183 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 05 10:57:44.183 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Dec 05 10:57:44.183 INFO [stderr] Dec 05 10:57:49.390 INFO [stderr] error[E0432]: unresolved import `secp256k1` Dec 05 10:57:49.391 INFO [stderr] --> benches/public_key.rs:8:5 Dec 05 10:57:49.391 INFO [stderr] | Dec 05 10:57:49.391 INFO [stderr] 8 | use secp256k1::PublicKey; Dec 05 10:57:49.392 INFO [stderr] | ^^^^^^^^^ maybe a missing `extern crate secp256k1;`? Dec 05 10:57:49.392 INFO [stderr] Dec 05 10:57:49.736 INFO [stderr] error: aborting due to previous error Dec 05 10:57:49.737 INFO [stderr] Dec 05 10:57:49.737 INFO [stderr] For more information about this error, try `rustc --explain E0432`. Dec 05 10:57:49.792 INFO [stderr] error: Could not compile `libsecp256k1-rs`. Dec 05 10:57:49.792 INFO [stderr] warning: build failed, waiting for other jobs to finish... Dec 05 10:57:50.455 INFO [stderr] error[E0432]: unresolved import `secp256k1` Dec 05 10:57:50.455 INFO [stderr] --> benches/sign.rs:11:5 Dec 05 10:57:50.455 INFO [stderr] | Dec 05 10:57:50.455 INFO [stderr] 11 | use secp256k1::{sign, Message, SecretKey}; Dec 05 10:57:50.455 INFO [stderr] | ^^^^^^^^^ maybe a missing `extern crate secp256k1;`? Dec 05 10:57:50.455 INFO [stderr] Dec 05 10:57:50.522 INFO [stderr] error: aborting due to previous error Dec 05 10:57:50.522 INFO [stderr] Dec 05 10:57:50.522 INFO [stderr] For more information about this error, try `rustc --explain E0432`. Dec 05 10:57:50.539 INFO [stderr] error: Could not compile `libsecp256k1-rs`. Dec 05 10:57:50.539 INFO [stderr] warning: build failed, waiting for other jobs to finish... Dec 05 10:57:50.787 INFO [stderr] error[E0432]: unresolved import `secp256k1` Dec 05 10:57:50.787 INFO [stderr] --> benches/signature.rs:8:5 Dec 05 10:57:50.787 INFO [stderr] | Dec 05 10:57:50.787 INFO [stderr] 8 | use secp256k1::Signature; Dec 05 10:57:50.787 INFO [stderr] | ^^^^^^^^^ maybe a missing `extern crate secp256k1;`? Dec 05 10:57:50.787 INFO [stderr] Dec 05 10:57:50.995 INFO [stderr] error: aborting due to previous error Dec 05 10:57:50.995 INFO [stderr] Dec 05 10:57:50.995 INFO [stderr] For more information about this error, try `rustc --explain E0432`. Dec 05 10:57:51.019 INFO [stderr] error: Could not compile `libsecp256k1-rs`. Dec 05 10:57:51.019 INFO [stderr] warning: build failed, waiting for other jobs to finish... Dec 05 10:57:51.547 INFO [stderr] warning: unused `std::result::Result` that must be used Dec 05 10:57:51.547 INFO [stderr] --> src/secp256k1/keys.rs:157:9 Dec 05 10:57:51.547 INFO [stderr] | Dec 05 10:57:51.547 INFO [stderr] 157 | write!(f, "{}", self.to_hex(true)); Dec 05 10:57:51.547 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dec 05 10:57:51.547 INFO [stderr] | Dec 05 10:57:51.547 INFO [stderr] = note: #[warn(unused_must_use)] on by default Dec 05 10:57:51.547 INFO [stderr] = note: this `Result` may be an `Err` variant, which should be handled Dec 05 10:57:51.547 INFO [stderr] = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info) Dec 05 10:57:51.547 INFO [stderr] Dec 05 10:57:53.246 INFO [stderr] error: build failed Dec 05 10:57:53.251 INFO [stderr] su: No module specific data is present Dec 05 10:57:54.285 INFO running `"docker" "inspect" "3b2c14af4b26325ca8b4d057c05741e17b1e0806c74dd5ef4dc7f4e9a2f3dd90"` Dec 05 10:57:54.635 INFO running `"docker" "rm" "-f" "3b2c14af4b26325ca8b4d057c05741e17b1e0806c74dd5ef4dc7f4e9a2f3dd90"` Dec 05 10:57:54.979 INFO [stdout] 3b2c14af4b26325ca8b4d057c05741e17b1e0806c74dd5ef4dc7f4e9a2f3dd90