[INFO] crate timeit-tool 0.1.4 is already in cache [INFO] extracting crate timeit-tool 0.1.4 into work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/timeit-tool/0.1.4 [INFO] extracting crate timeit-tool 0.1.4 into work/ex/pr-57967/sources/try#7fea0229842e79db1159ea58ad9a653b288efee9/reg/timeit-tool/0.1.4 [INFO] validating manifest of timeit-tool-0.1.4 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 timeit-tool-0.1.4 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 timeit-tool-0.1.4 [INFO] finished frobbing timeit-tool-0.1.4 [INFO] frobbed toml for timeit-tool-0.1.4 written to work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/timeit-tool/0.1.4/Cargo.toml [INFO] started frobbing timeit-tool-0.1.4 [INFO] finished frobbing timeit-tool-0.1.4 [INFO] frobbed toml for timeit-tool-0.1.4 written to work/ex/pr-57967/sources/try#7fea0229842e79db1159ea58ad9a653b288efee9/reg/timeit-tool/0.1.4/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 timeit-tool-0.1.4 against master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54 for pr-57967 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-3/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/timeit-tool/0.1.4:/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] 970e3874f2d2a549a5552d389a01e5b9d451dae6e57248ebbd897170fe962e48 [INFO] running `"docker" "start" "-a" "970e3874f2d2a549a5552d389a01e5b9d451dae6e57248ebbd897170fe962e48"` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/src/main.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 binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = 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] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `timeit`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] [stderr] Compiling timeit-tool v0.1.4 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.01s [INFO] running `"docker" "inspect" "970e3874f2d2a549a5552d389a01e5b9d451dae6e57248ebbd897170fe962e48"` [INFO] running `"docker" "rm" "-f" "970e3874f2d2a549a5552d389a01e5b9d451dae6e57248ebbd897170fe962e48"` [INFO] [stdout] 970e3874f2d2a549a5552d389a01e5b9d451dae6e57248ebbd897170fe962e48 [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-3/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/timeit-tool/0.1.4:/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] ac28b0f2f42d9386c04da8fff92c4e567b152a7433ce8074b2efd45323cc8f7b [INFO] running `"docker" "start" "-a" "ac28b0f2f42d9386c04da8fff92c4e567b152a7433ce8074b2efd45323cc8f7b"` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/src/main.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 binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = 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] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `timeit`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] [stderr] Compiling timeit-tool v0.1.4 (/opt/crater/workdir) [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.63s [INFO] running `"docker" "inspect" "ac28b0f2f42d9386c04da8fff92c4e567b152a7433ce8074b2efd45323cc8f7b"` [INFO] running `"docker" "rm" "-f" "ac28b0f2f42d9386c04da8fff92c4e567b152a7433ce8074b2efd45323cc8f7b"` [INFO] [stdout] ac28b0f2f42d9386c04da8fff92c4e567b152a7433ce8074b2efd45323cc8f7b [INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-57967/worker-3/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-57967/sources/master#c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54/reg/timeit-tool/0.1.4:/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] f1eace13a2a3ae410a831f2f633c9b17a80d176173f4725d3a4412fa5de2c7d3 [INFO] running `"docker" "start" "-a" "f1eace13a2a3ae410a831f2f633c9b17a80d176173f4725d3a4412fa5de2c7d3"` [INFO] [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently [INFO] [stderr] disables Cargo from automatically inferring other binary targets. [INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following [INFO] [stderr] files will be included as a binary target: [INFO] [stderr] [INFO] [stderr] * /opt/crater/workdir/src/main.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 binary target today. You can future-proof yourself [INFO] [stderr] and disable this warning by adding `autobins = 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] warning: path `/opt/crater/workdir/src/main.rs` was erroneously implicitly accepted for binary `timeit`, [INFO] [stderr] please set bin.path in Cargo.toml [INFO] [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.02s [INFO] [stderr] Running /opt/crater/target/debug/deps/timeit-ba2a2f8ecd65ec2f [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] running `"docker" "inspect" "f1eace13a2a3ae410a831f2f633c9b17a80d176173f4725d3a4412fa5de2c7d3"` [INFO] running `"docker" "rm" "-f" "f1eace13a2a3ae410a831f2f633c9b17a80d176173f4725d3a4412fa5de2c7d3"` [INFO] [stdout] f1eace13a2a3ae410a831f2f633c9b17a80d176173f4725d3a4412fa5de2c7d3