Nov 18 10:58:24.464 INFO testing google-monitoring3-cli-1.0.7+20171204 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 10:58:24.464 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:24.685 INFO [stdout] 6d4b7de5ca17d7522c92004ee6473edc682b8d970c0c2f31e8d7b2617ede69ae
Nov 18 10:58:24.689 INFO running `"docker" "start" "-a" "6d4b7de5ca17d7522c92004ee6473edc682b8d970c0c2f31e8d7b2617ede69ae"`
Nov 18 10:58:25.187 INFO [stderr] usermod: no changes
Nov 18 10:58:25.213 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:58:25.213 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:58:25.213 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:58:25.213 INFO [stderr] files will be included as a binary target:
Nov 18 10:58:25.213 INFO [stderr] 
Nov 18 10:58:25.213 INFO [stderr] * /source/src/main.rs
Nov 18 10:58:25.213 INFO [stderr] 
Nov 18 10:58:25.213 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:58:25.213 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:58:25.213 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:58:25.213 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:58:25.213 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:58:25.213 INFO [stderr] 
Nov 18 10:58:25.213 INFO [stderr] For more information on this warning you can consult
Nov 18 10:58:25.213 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:58:25.213 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `monitoring3`,
Nov 18 10:58:25.213 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:58:25.403 INFO [stderr]    Compiling google-monitoring3 v1.0.8+20181009
Nov 18 10:58:36.015 INFO [stderr]    Compiling google-monitoring3-cli v1.0.7+20171204 (/source)
Nov 18 10:58:56.769 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 31.56s
Nov 18 10:58:56.781 INFO [stderr] su: No module specific data is present
Nov 18 10:58:57.978 INFO running `"docker" "inspect" "6d4b7de5ca17d7522c92004ee6473edc682b8d970c0c2f31e8d7b2617ede69ae"`
Nov 18 10:58:58.323 INFO running `"docker" "rm" "-f" "6d4b7de5ca17d7522c92004ee6473edc682b8d970c0c2f31e8d7b2617ede69ae"`
Nov 18 10:58:58.629 INFO [stdout] 6d4b7de5ca17d7522c92004ee6473edc682b8d970c0c2f31e8d7b2617ede69ae
Nov 18 10:58:58.633 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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.079 INFO [stdout] 9ab8e1e3e6f78134801c2ae20dfcce2d2b1780929277f1108f39285eeb134fcf
Nov 18 10:58:59.087 INFO running `"docker" "start" "-a" "9ab8e1e3e6f78134801c2ae20dfcce2d2b1780929277f1108f39285eeb134fcf"`
Nov 18 10:58:59.687 INFO [stderr] usermod: no changes
Nov 18 10:58:59.715 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:58:59.715 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:58:59.715 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:58:59.715 INFO [stderr] files will be included as a binary target:
Nov 18 10:58:59.715 INFO [stderr] 
Nov 18 10:58:59.715 INFO [stderr] * /source/src/main.rs
Nov 18 10:58:59.715 INFO [stderr] 
Nov 18 10:58:59.715 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:58:59.715 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:58:59.715 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:58:59.715 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:58:59.715 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:58:59.715 INFO [stderr] 
Nov 18 10:58:59.715 INFO [stderr] For more information on this warning you can consult
Nov 18 10:58:59.715 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:58:59.715 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `monitoring3`,
Nov 18 10:58:59.715 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:58:59.849 INFO [stderr]    Compiling google-monitoring3-cli v1.0.7+20171204 (/source)
Nov 18 10:59:06.299 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.60s
Nov 18 10:59:06.315 INFO [stderr] su: No module specific data is present
Nov 18 10:59:07.064 INFO running `"docker" "inspect" "9ab8e1e3e6f78134801c2ae20dfcce2d2b1780929277f1108f39285eeb134fcf"`
Nov 18 10:59:07.333 INFO running `"docker" "rm" "-f" "9ab8e1e3e6f78134801c2ae20dfcce2d2b1780929277f1108f39285eeb134fcf"`
Nov 18 10:59:07.594 INFO [stdout] 9ab8e1e3e6f78134801c2ae20dfcce2d2b1780929277f1108f39285eeb134fcf
Nov 18 10:59:07.597 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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.959 INFO [stdout] 0c46aaa47ee8cf80e2eff2a0f756b18a6e9ca07a941e79e6a3b2ed13ce1c3e8e
Nov 18 10:59:07.959 INFO running `"docker" "start" "-a" "0c46aaa47ee8cf80e2eff2a0f756b18a6e9ca07a941e79e6a3b2ed13ce1c3e8e"`
Nov 18 10:59:09.143 INFO [stderr] usermod: no changes
Nov 18 10:59:09.203 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:59:09.203 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:59:09.203 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:59:09.203 INFO [stderr] files will be included as a binary target:
Nov 18 10:59:09.203 INFO [stderr] 
Nov 18 10:59:09.203 INFO [stderr] * /source/src/main.rs
Nov 18 10:59:09.203 INFO [stderr] 
Nov 18 10:59:09.203 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:59:09.203 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:59:09.203 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:59:09.203 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:59:09.203 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:59:09.203 INFO [stderr] 
Nov 18 10:59:09.203 INFO [stderr] For more information on this warning you can consult
Nov 18 10:59:09.203 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:59:09.203 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `monitoring3`,
Nov 18 10:59:09.203 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:59:09.413 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.25s
Nov 18 10:59:09.439 INFO [stderr]      Running /target/debug/deps/monitoring3-d8b294537b66e4a5
Nov 18 10:59:09.441 INFO [stdout] 
Nov 18 10:59:09.441 INFO [stdout] running 0 tests
Nov 18 10:59:09.441 INFO [stdout] 
Nov 18 10:59:09.441 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:59:09.441 INFO [stdout] 
Nov 18 10:59:09.447 INFO [stderr] su: No module specific data is present
Nov 18 10:59:10.277 INFO running `"docker" "inspect" "0c46aaa47ee8cf80e2eff2a0f756b18a6e9ca07a941e79e6a3b2ed13ce1c3e8e"`
Nov 18 10:59:10.489 INFO running `"docker" "rm" "-f" "0c46aaa47ee8cf80e2eff2a0f756b18a6e9ca07a941e79e6a3b2ed13ce1c3e8e"`
Nov 18 10:59:10.722 INFO [stdout] 0c46aaa47ee8cf80e2eff2a0f756b18a6e9ca07a941e79e6a3b2ed13ce1c3e8e