Nov 18 10:49:23.123 INFO testing google-servicecontrol1-cli-1.0.7+20171202 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982 Nov 18 10:49:23.123 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Nov 18 10:49:23.266 INFO [stdout] 176c1360bdfd792773cefd04326e61ac05fcd7055f775615b437d92533a4f066 Nov 18 10:49:23.268 INFO running `"docker" "start" "-a" "176c1360bdfd792773cefd04326e61ac05fcd7055f775615b437d92533a4f066"` Nov 18 10:49:23.737 INFO [stderr] usermod: no changes Nov 18 10:49:23.759 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:49:23.759 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:49:23.759 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:49:23.759 INFO [stderr] files will be included as a binary target: Nov 18 10:49:23.759 INFO [stderr] Nov 18 10:49:23.759 INFO [stderr] * /source/src/main.rs Nov 18 10:49:23.759 INFO [stderr] Nov 18 10:49:23.759 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:49:23.759 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:49:23.759 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:49:23.759 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:49:23.759 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:49:23.759 INFO [stderr] Nov 18 10:49:23.759 INFO [stderr] For more information on this warning you can consult Nov 18 10:49:23.759 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:49:23.759 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `servicecontrol1`, Nov 18 10:49:23.759 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:49:23.955 INFO [stderr] Compiling google-servicecontrol1 v1.0.8+20181008 Nov 18 10:49:31.641 INFO [stderr] Compiling google-servicecontrol1-cli v1.0.7+20171202 (/source) Nov 18 10:49:53.068 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 29.31s Nov 18 10:49:53.081 INFO [stderr] su: No module specific data is present Nov 18 10:49:53.755 INFO running `"docker" "inspect" "176c1360bdfd792773cefd04326e61ac05fcd7055f775615b437d92533a4f066"` Nov 18 10:49:54.067 INFO running `"docker" "rm" "-f" "176c1360bdfd792773cefd04326e61ac05fcd7055f775615b437d92533a4f066"` Nov 18 10:49:54.377 INFO [stdout] 176c1360bdfd792773cefd04326e61ac05fcd7055f775615b437d92533a4f066 Nov 18 10:49:54.381 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Nov 18 10:49:54.867 INFO [stdout] 746204102f1a7b647079ca42a9bab3386c3497d668ea14974b3a35ad32650af6 Nov 18 10:49:54.869 INFO running `"docker" "start" "-a" "746204102f1a7b647079ca42a9bab3386c3497d668ea14974b3a35ad32650af6"` Nov 18 10:49:56.787 INFO [stderr] usermod: no changes Nov 18 10:49:56.851 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:49:56.851 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:49:56.852 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:49:56.852 INFO [stderr] files will be included as a binary target: Nov 18 10:49:56.852 INFO [stderr] Nov 18 10:49:56.853 INFO [stderr] * /source/src/main.rs Nov 18 10:49:56.853 INFO [stderr] Nov 18 10:49:56.853 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:49:56.853 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:49:56.854 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:49:56.854 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:49:56.854 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:49:56.854 INFO [stderr] Nov 18 10:49:56.855 INFO [stderr] For more information on this warning you can consult Nov 18 10:49:56.855 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:49:56.855 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `servicecontrol1`, Nov 18 10:49:56.855 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:49:57.103 INFO [stderr] Compiling google-servicecontrol1-cli v1.0.7+20171202 (/source) Nov 18 10:50:02.820 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 6.01s Nov 18 10:50:02.839 INFO [stderr] su: No module specific data is present Nov 18 10:50:03.310 INFO running `"docker" "inspect" "746204102f1a7b647079ca42a9bab3386c3497d668ea14974b3a35ad32650af6"` Nov 18 10:50:03.551 INFO running `"docker" "rm" "-f" "746204102f1a7b647079ca42a9bab3386c3497d668ea14974b3a35ad32650af6"` Nov 18 10:50:03.837 INFO [stdout] 746204102f1a7b647079ca42a9bab3386c3497d668ea14974b3a35ad32650af6 Nov 18 10:50:03.842 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"` Nov 18 10:50:04.208 INFO [stdout] f8d331c039f80fc5cab3f1f61e7f73663d7f2ac0568a9026840ac9eb3f951e46 Nov 18 10:50:04.219 INFO running `"docker" "start" "-a" "f8d331c039f80fc5cab3f1f61e7f73663d7f2ac0568a9026840ac9eb3f951e46"` Nov 18 10:50:05.572 INFO [stderr] usermod: no changes Nov 18 10:50:05.615 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:50:05.615 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:50:05.615 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:50:05.615 INFO [stderr] files will be included as a binary target: Nov 18 10:50:05.615 INFO [stderr] Nov 18 10:50:05.615 INFO [stderr] * /source/src/main.rs Nov 18 10:50:05.615 INFO [stderr] Nov 18 10:50:05.615 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:50:05.615 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:50:05.615 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:50:05.615 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:50:05.615 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:50:05.615 INFO [stderr] Nov 18 10:50:05.615 INFO [stderr] For more information on this warning you can consult Nov 18 10:50:05.615 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:50:05.615 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `servicecontrol1`, Nov 18 10:50:05.615 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:50:05.807 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.19s Nov 18 10:50:05.823 INFO [stderr] Running /target/debug/deps/servicecontrol1-9f15bf54b9efae5f Nov 18 10:50:05.823 INFO [stdout] Nov 18 10:50:05.823 INFO [stdout] running 0 tests Nov 18 10:50:05.824 INFO [stdout] Nov 18 10:50:05.824 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 10:50:05.824 INFO [stdout] Nov 18 10:50:05.831 INFO [stderr] su: No module specific data is present Nov 18 10:50:06.609 INFO running `"docker" "inspect" "f8d331c039f80fc5cab3f1f61e7f73663d7f2ac0568a9026840ac9eb3f951e46"` Nov 18 10:50:06.891 INFO running `"docker" "rm" "-f" "f8d331c039f80fc5cab3f1f61e7f73663d7f2ac0568a9026840ac9eb3f951e46"` Nov 18 10:50:07.195 INFO [stdout] f8d331c039f80fc5cab3f1f61e7f73663d7f2ac0568a9026840ac9eb3f951e46