Nov 18 10:58:25.056 INFO testing google-monitoring3-cli-1.0.7+20171204 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 10:58:25.056 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:58:25.252 INFO [stdout] 4400f9544d0c9ef887b2f532af27f5aea2d461260794977641b2936962ba2fc3
Nov 18 10:58:25.254 INFO running `"docker" "start" "-a" "4400f9544d0c9ef887b2f532af27f5aea2d461260794977641b2936962ba2fc3"`
Nov 18 10:58:25.730 INFO [stderr] usermod: no changes
Nov 18 10:58:25.763 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:58:25.763 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:58:25.763 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:58:25.763 INFO [stderr] files will be included as a binary target:
Nov 18 10:58:25.763 INFO [stderr] 
Nov 18 10:58:25.763 INFO [stderr] * /source/src/main.rs
Nov 18 10:58:25.763 INFO [stderr] 
Nov 18 10:58:25.763 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:58:25.763 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:58:25.763 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:58:25.763 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:58:25.763 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:58:25.763 INFO [stderr] 
Nov 18 10:58:25.763 INFO [stderr] For more information on this warning you can consult
Nov 18 10:58:25.763 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:58:25.763 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `monitoring3`,
Nov 18 10:58:25.763 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:58:25.894 INFO [stderr]    Compiling google-monitoring3 v1.0.8+20181009
Nov 18 10:58:36.275 INFO [stderr]    Compiling google-monitoring3-cli v1.0.7+20171204 (/source)
Nov 18 10:58:58.439 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 32.69s
Nov 18 10:58:58.459 INFO [stderr] su: No module specific data is present
Nov 18 10:58:59.052 INFO running `"docker" "inspect" "4400f9544d0c9ef887b2f532af27f5aea2d461260794977641b2936962ba2fc3"`
Nov 18 10:58:59.145 INFO running `"docker" "rm" "-f" "4400f9544d0c9ef887b2f532af27f5aea2d461260794977641b2936962ba2fc3"`
Nov 18 10:58:59.253 INFO [stdout] 4400f9544d0c9ef887b2f532af27f5aea2d461260794977641b2936962ba2fc3
Nov 18 10:58:59.254 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:58:59.589 INFO [stdout] cf0dd5935aada8d2bc84efd59529dcc2947eb124c4a3cd322d8809c3c64f4a41
Nov 18 10:58:59.592 INFO running `"docker" "start" "-a" "cf0dd5935aada8d2bc84efd59529dcc2947eb124c4a3cd322d8809c3c64f4a41"`
Nov 18 10:59:00.038 INFO [stderr] usermod: no changes
Nov 18 10:59:00.083 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:59:00.083 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:59:00.083 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:59:00.083 INFO [stderr] files will be included as a binary target:
Nov 18 10:59:00.083 INFO [stderr] 
Nov 18 10:59:00.083 INFO [stderr] * /source/src/main.rs
Nov 18 10:59:00.083 INFO [stderr] 
Nov 18 10:59:00.083 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:59:00.083 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:59:00.083 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:59:00.083 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:59:00.083 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:59:00.083 INFO [stderr] 
Nov 18 10:59:00.083 INFO [stderr] For more information on this warning you can consult
Nov 18 10:59:00.083 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:59:00.083 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `monitoring3`,
Nov 18 10:59:00.083 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:59:00.208 INFO [stderr]    Compiling google-monitoring3-cli v1.0.7+20171204 (/source)
Nov 18 10:59:06.143 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.07s
Nov 18 10:59:06.151 INFO [stderr] su: No module specific data is present
Nov 18 10:59:06.763 INFO running `"docker" "inspect" "cf0dd5935aada8d2bc84efd59529dcc2947eb124c4a3cd322d8809c3c64f4a41"`
Nov 18 10:59:07.101 INFO running `"docker" "rm" "-f" "cf0dd5935aada8d2bc84efd59529dcc2947eb124c4a3cd322d8809c3c64f4a41"`
Nov 18 10:59:07.363 INFO [stdout] cf0dd5935aada8d2bc84efd59529dcc2947eb124c4a3cd322d8809c3c64f4a41
Nov 18 10:59:07.367 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:59:07.707 INFO [stdout] 52117ec9d57239f1e8b35440b3dc33266da4445ae0c6bc00cadc137e9a4d9326
Nov 18 10:59:07.707 INFO running `"docker" "start" "-a" "52117ec9d57239f1e8b35440b3dc33266da4445ae0c6bc00cadc137e9a4d9326"`
Nov 18 10:59:09.006 INFO [stderr] usermod: no changes
Nov 18 10:59:09.055 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:59:09.055 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:59:09.055 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:59:09.055 INFO [stderr] files will be included as a binary target:
Nov 18 10:59:09.055 INFO [stderr] 
Nov 18 10:59:09.055 INFO [stderr] * /source/src/main.rs
Nov 18 10:59:09.055 INFO [stderr] 
Nov 18 10:59:09.055 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:59:09.055 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:59:09.055 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:59:09.055 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:59:09.055 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:59:09.055 INFO [stderr] 
Nov 18 10:59:09.055 INFO [stderr] For more information on this warning you can consult
Nov 18 10:59:09.055 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:59:09.055 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `monitoring3`,
Nov 18 10:59:09.055 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:59:09.223 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.20s
Nov 18 10:59:09.255 INFO [stderr]      Running /target/debug/deps/monitoring3-2752ac9cf594dbdc
Nov 18 10:59:09.257 INFO [stdout] 
Nov 18 10:59:09.257 INFO [stdout] running 0 tests
Nov 18 10:59:09.257 INFO [stdout] 
Nov 18 10:59:09.257 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:59:09.257 INFO [stdout] 
Nov 18 10:59:09.263 INFO [stderr] su: No module specific data is present
Nov 18 10:59:09.913 INFO running `"docker" "inspect" "52117ec9d57239f1e8b35440b3dc33266da4445ae0c6bc00cadc137e9a4d9326"`
Nov 18 10:59:10.169 INFO running `"docker" "rm" "-f" "52117ec9d57239f1e8b35440b3dc33266da4445ae0c6bc00cadc137e9a4d9326"`
Nov 18 10:59:10.487 INFO [stdout] 52117ec9d57239f1e8b35440b3dc33266da4445ae0c6bc00cadc137e9a4d9326