[INFO] crate bulletproofs 1.0.2 is already in cache [INFO] extracting crate bulletproofs 1.0.2 into work/ex/pr-63565/sources/master#c43d03a19f326f4a323569328cc501e86eb6d22e/reg/bulletproofs/1.0.2 [INFO] extracting crate bulletproofs 1.0.2 into work/ex/pr-63565/sources/try#75eff020d0923c035c2fe220db4a0465cd847048/reg/bulletproofs/1.0.2 [INFO] validating manifest of bulletproofs-1.0.2 on toolchain master#c43d03a19f326f4a323569328cc501e86eb6d22e [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of bulletproofs-1.0.2 on toolchain try#75eff020d0923c035c2fe220db4a0465cd847048 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+75eff020d0923c035c2fe220db4a0465cd847048-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing bulletproofs-1.0.2 [INFO] removed 2 missing tests [INFO] finished frobbing bulletproofs-1.0.2 [INFO] frobbed toml for bulletproofs-1.0.2 written to work/ex/pr-63565/sources/master#c43d03a19f326f4a323569328cc501e86eb6d22e/reg/bulletproofs/1.0.2/Cargo.toml [INFO] started frobbing bulletproofs-1.0.2 [INFO] removed 2 missing tests [INFO] finished frobbing bulletproofs-1.0.2 [INFO] frobbed toml for bulletproofs-1.0.2 written to work/ex/pr-63565/sources/try#75eff020d0923c035c2fe220db4a0465cd847048/reg/bulletproofs/1.0.2/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+75eff020d0923c035c2fe220db4a0465cd847048-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+75eff020d0923c035c2fe220db4a0465cd847048-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] checking bulletproofs-1.0.2 against master#c43d03a19f326f4a323569328cc501e86eb6d22e for pr-63565 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-63565/worker-7/master#c43d03a19f326f4a323569328cc501e86eb6d22e:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-63565/sources/master#c43d03a19f326f4a323569328cc501e86eb6d22e/reg/bulletproofs/1.0.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+c43d03a19f326f4a323569328cc501e86eb6d22e-alt" "check" "--frozen" "--all" "--all-targets"` [INFO] [stdout] 975e57fc62f78db9c6b5ff9cb454bf73f25fbe2d1208435a18ccc7a4514ad366 [INFO] running `"docker" "start" "-a" "975e57fc62f78db9c6b5ff9cb454bf73f25fbe2d1208435a18ccc7a4514ad366"` [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/crater/workdir/tests/r1cs.rs [INFO] [stderr] * /opt/crater/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] Checking merlin v1.2.0 [INFO] [stderr] Compiling curve25519-dalek v1.2.3 [INFO] [stderr] Checking bulletproofs v1.0.2 (/opt/crater/workdir) [INFO] [stderr] error: couldn't read src/range_proof/../docs/range-proof-protocol.md: No such file or directory (os error 2) [INFO] [stderr] --> src/range_proof/mod.rs:2:18 [INFO] [stderr] | [INFO] [stderr] 2 | #![doc(include = "../docs/range-proof-protocol.md")] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ couldn't read file [INFO] [stderr] [INFO] [stderr] error: couldn't read src/range_proof/../docs/range-proof-protocol.md: No such file or directory (os error 2) [INFO] [stderr] --> src/range_proof/mod.rs:2:18 [INFO] [stderr] | [INFO] [stderr] 2 | #![doc(include = "../docs/range-proof-protocol.md")] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ couldn't read file [INFO] [stderr] [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] error: aborting due to previous error [INFO] [stderr] [INFO] [stderr] error: Could not compile `bulletproofs`. [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stderr] error: aborting due to previous error [INFO] [stderr] [INFO] [stderr] error: Could not compile `bulletproofs`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "975e57fc62f78db9c6b5ff9cb454bf73f25fbe2d1208435a18ccc7a4514ad366"` [INFO] running `"docker" "rm" "-f" "975e57fc62f78db9c6b5ff9cb454bf73f25fbe2d1208435a18ccc7a4514ad366"` [INFO] [stdout] 975e57fc62f78db9c6b5ff9cb454bf73f25fbe2d1208435a18ccc7a4514ad366