[INFO] fetching crate bulletproofs 1.0.4... [INFO] checking bulletproofs-1.0.4 against master#2748a9fd93dd1a00a4521f4f16de5befbf77f6cd for pr-62262-1 [INFO] extracting crate bulletproofs 1.0.4 into /workspace/builds/worker-7/source [INFO] validating manifest of crates.io crate bulletproofs 1.0.4 on toolchain 2748a9fd93dd1a00a4521f4f16de5befbf77f6cd [INFO] running `"/workspace/cargo-home/bin/cargo" "+2748a9fd93dd1a00a4521f4f16de5befbf77f6cd" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started tweaking crates.io crate bulletproofs 1.0.4 [INFO] removed 2 missing tests [INFO] finished tweaking crates.io crate bulletproofs 1.0.4 [INFO] tweaked toml for crates.io crate bulletproofs 1.0.4 written to /workspace/builds/worker-7/source/Cargo.toml [INFO] running `"/workspace/cargo-home/bin/cargo" "+2748a9fd93dd1a00a4521f4f16de5befbf77f6cd" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/workspace/cargo-home/bin/cargo" "+2748a9fd93dd1a00a4521f4f16de5befbf77f6cd" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /workspace/builds/worker-7/source/tests/r1cs.rs [INFO] [stderr] * /workspace/builds/worker-7/source/tests/range_proof.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] running `"docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=0" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--network" "none" "rustops/crates-build-env" "/opt/rustwide/cargo-home/bin/cargo" "+2748a9fd93dd1a00a4521f4f16de5befbf77f6cd" "check" "--frozen" "--all" "--all-targets"` [INFO] [stderr] WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. [INFO] [stdout] 9431d84a212cccefd6074335102a02e0bb8d983e9abef27029a63f29eb6d3bf2 [INFO] running `"docker" "start" "-a" "9431d84a212cccefd6074335102a02e0bb8d983e9abef27029a63f29eb6d3bf2"` [INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other test targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a test target: [INFO] [stderr] [INFO] [stderr] * /opt/rustwide/workdir/tests/r1cs.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/range_proof.rs [INFO] [stderr] [INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be [INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autotests = false` to your [package] [INFO] [stderr] section. You may also move the files to a location where Cargo would not [INFO] [stderr] automatically infer them to be a target, such as in subfolders. [INFO] [stderr] [INFO] [stderr] For more information on this warning you can consult [INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330 [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Compiling byteorder v1.3.2 [INFO] [stderr] Compiling subtle v2.2.1 [INFO] [stderr] Checking keccak v0.1.0 [INFO] [stderr] Checking rand_core v0.3.1 [INFO] [stderr] Compiling clear_on_drop v0.2.3 [INFO] [stderr] Checking tinytemplate v1.0.2 [INFO] [stderr] Checking rand_chacha v0.1.1 [INFO] [stderr] Checking rand_hc v0.1.0 [INFO] [stderr] Checking rand_isaac v0.1.1 [INFO] [stderr] Checking rand_xorshift v0.1.1 [INFO] [stderr] Checking rand v0.6.5 [INFO] [stderr] Compiling curve25519-dalek v1.2.3 [INFO] [stderr] Checking regex-automata v0.1.8 [INFO] [stderr] Checking block-buffer v0.7.3 [INFO] [stderr] Checking rand_xoshiro v0.1.0 [INFO] [stderr] Checking criterion-plot v0.3.1 [INFO] [stderr] Checking merlin v1.2.1 [INFO] [stderr] Checking bincode v1.2.0 [INFO] [stderr] Checking sha3 v0.8.2 [INFO] [stderr] Checking bstr v0.2.8 [INFO] [stderr] Checking csv v1.1.1 [INFO] [stderr] Checking criterion v0.2.11 [INFO] [stderr] Checking bulletproofs v1.0.4 (/opt/rustwide/workdir) [INFO] [stderr] warning: the item `bincode` is imported redundantly [INFO] [stderr] --> src/range_proof/mod.rs:531:13 [INFO] [stderr] | [INFO] [stderr] 531 | use bincode; [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/lib.rs:26:1 [INFO] [stderr] | [INFO] [stderr] 26 | extern crate bincode; [INFO] [stderr] | --------------------- the item `bincode` is already imported here [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(unused_imports)]` on by default [INFO] [stderr] [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 19.74s [INFO] running `"docker" "inspect" "9431d84a212cccefd6074335102a02e0bb8d983e9abef27029a63f29eb6d3bf2"` [INFO] running `"docker" "rm" "-f" "9431d84a212cccefd6074335102a02e0bb8d983e9abef27029a63f29eb6d3bf2"` [INFO] [stdout] 9431d84a212cccefd6074335102a02e0bb8d983e9abef27029a63f29eb6d3bf2