[INFO] crate burst-pool 0.5.1 is already in cache [INFO] extracting crate burst-pool 0.5.1 into work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/burst-pool/0.5.1 [INFO] extracting crate burst-pool 0.5.1 into work/ex/pr-57967/sources/try#7fea0229842e79db1159ea58ad9a653b288efee9/reg/burst-pool/0.5.1 [INFO] validating manifest of burst-pool-0.5.1 on toolchain master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] validating manifest of burst-pool-0.5.1 on toolchain try#7fea0229842e79db1159ea58ad9a653b288efee9 [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+7fea0229842e79db1159ea58ad9a653b288efee9-alt" "read-manifest" "--manifest-path" "Cargo.toml"` [INFO] started frobbing burst-pool-0.5.1 [INFO] finished frobbing burst-pool-0.5.1 [INFO] frobbed toml for burst-pool-0.5.1 written to work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/burst-pool/0.5.1/Cargo.toml [INFO] started frobbing burst-pool-0.5.1 [INFO] finished frobbing burst-pool-0.5.1 [INFO] frobbed toml for burst-pool-0.5.1 written to work/ex/pr-57967/sources/try#7fea0229842e79db1159ea58ad9a653b288efee9/reg/burst-pool/0.5.1/Cargo.toml [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+7fea0229842e79db1159ea58ad9a653b288efee9-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+7fea0229842e79db1159ea58ad9a653b288efee9-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"` [INFO] testing burst-pool-0.5.1 against master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54 for pr-57967 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-7/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/burst-pool/0.5.1:/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" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "build" "--frozen"` [INFO] [stdout] 7fb403fdfb59ead4f2fb8e9bee2d4c978e13f2b366092dd820f68db157e4dfe8 [INFO] running `"docker" "start" "-a" "7fb403fdfb59ead4f2fb8e9bee2d4c978e13f2b366092dd820f68db157e4dfe8"` [INFO] [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other benchmark targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a benchmark target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/benches/settings.rs [INFO] [stderr] * /opt/crater/workdir/benches/stats.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 benchmark target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobenches = 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 burst-pool v0.5.1 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.68s [INFO] running `"docker" "inspect" "7fb403fdfb59ead4f2fb8e9bee2d4c978e13f2b366092dd820f68db157e4dfe8"` [INFO] running `"docker" "rm" "-f" "7fb403fdfb59ead4f2fb8e9bee2d4c978e13f2b366092dd820f68db157e4dfe8"` [INFO] [stdout] 7fb403fdfb59ead4f2fb8e9bee2d4c978e13f2b366092dd820f68db157e4dfe8 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-7/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/burst-pool/0.5.1:/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" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "test" "--frozen" "--no-run"` [INFO] [stdout] 6e4fd3fbcebc386394593cc45649bb54a4c177a7e944841b07c580ab0fcfeb14 [INFO] running `"docker" "start" "-a" "6e4fd3fbcebc386394593cc45649bb54a4c177a7e944841b07c580ab0fcfeb14"` [INFO] [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other benchmark targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a benchmark target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/benches/settings.rs [INFO] [stderr] * /opt/crater/workdir/benches/stats.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 benchmark target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobenches = 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 burst-pool v0.5.1 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.87s [INFO] running `"docker" "inspect" "6e4fd3fbcebc386394593cc45649bb54a4c177a7e944841b07c580ab0fcfeb14"` [INFO] running `"docker" "rm" "-f" "6e4fd3fbcebc386394593cc45649bb54a4c177a7e944841b07c580ab0fcfeb14"` [INFO] [stdout] 6e4fd3fbcebc386394593cc45649bb54a4c177a7e944841b07c580ab0fcfeb14 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-7/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/burst-pool/0.5.1:/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" "+c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54-alt" "test" "--frozen"` [INFO] [stdout] c61e189021c60df99f363276a88e0b1999d70966001bc7cb63876789b1696b0f [INFO] running `"docker" "start" "-a" "c61e189021c60df99f363276a88e0b1999d70966001bc7cb63876789b1696b0f"` [INFO] [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other benchmark targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a benchmark target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/benches/settings.rs [INFO] [stderr] * /opt/crater/workdir/benches/stats.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 benchmark target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobenches = 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] Finished dev [unoptimized + debuginfo] target(s) in 0.08s [INFO] [stderr] Running /opt/crater/target/debug/deps/burst_pool-acc4b27d203b9b3a [INFO] [stderr] Doc-tests burst_pool [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] running 1 test [INFO] [stdout] test lib.rs - (line 66) ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out [INFO] [stdout] [INFO] running `"docker" "inspect" "c61e189021c60df99f363276a88e0b1999d70966001bc7cb63876789b1696b0f"` [INFO] running `"docker" "rm" "-f" "c61e189021c60df99f363276a88e0b1999d70966001bc7cb63876789b1696b0f"` [INFO] [stdout] c61e189021c60df99f363276a88e0b1999d70966001bc7cb63876789b1696b0f