[INFO] crate bulletproofs 1.0.4 is already in cache [INFO] testing bulletproofs-1.0.4 against 1.38.0 for beta-1.39-1 [INFO] extracting crate bulletproofs 1.0.4 into work/builds/worker-6/source [INFO] validating manifest of crates.io crate bulletproofs 1.0.4 on toolchain 1.38.0 [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+1.38.0" "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 work/builds/worker-6/source/Cargo.toml [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+1.38.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/big/crater/work/cargo-home/bin/cargo" "+1.38.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"docker" "create" "-v" "/big/crater/work/builds/worker-6/target:/opt/rustwide/target:rw,Z" "-v" "/big/crater/work/builds/worker-6/source:/opt/rustwide/workdir:ro,Z" "-v" "/big/crater/work/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/big/crater/work/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-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" "+1.38.0" "build" "--frozen"` [INFO] [stdout] c8f1cbac540761ba7280ca5278d81312238f25647f61482f36909ce700383590 [INFO] running `"docker" "start" "-a" "c8f1cbac540761ba7280ca5278d81312238f25647f61482f36909ce700383590"` [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/range_proof.rs [INFO] [stderr] * /opt/rustwide/workdir/tests/r1cs.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] Compiling subtle v2.2.1 [INFO] [stderr] Compiling merlin v1.2.1 [INFO] [stderr] Compiling curve25519-dalek v1.2.3 [INFO] [stderr] Compiling bulletproofs v1.0.4 (/opt/rustwide/workdir) [INFO] [stderr] error[E0554]: `#![feature]` may not be used on the stable release channel [INFO] [stderr] --> src/lib.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #![feature(nll)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error[E0554]: `#![feature]` may not be used on the stable release channel [INFO] [stderr] --> src/lib.rs:2:1 [INFO] [stderr] | [INFO] [stderr] 2 | #![feature(external_doc)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error[E0554]: `#![feature]` may not be used on the stable release channel [INFO] [stderr] --> src/lib.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | #![feature(try_trait)] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] error: aborting due to 3 previous errors [INFO] [stderr] [INFO] [stderr] For more information about this error, try `rustc --explain E0554`. [INFO] [stderr] error: Could not compile `bulletproofs`. [INFO] [stderr] [INFO] [stderr] To learn more, run the command again with --verbose. [INFO] running `"docker" "inspect" "c8f1cbac540761ba7280ca5278d81312238f25647f61482f36909ce700383590"` [INFO] running `"docker" "rm" "-f" "c8f1cbac540761ba7280ca5278d81312238f25647f61482f36909ce700383590"` [INFO] [stdout] c8f1cbac540761ba7280ca5278d81312238f25647f61482f36909ce700383590