Nov 18 12:13:05.466 INFO testing google-cloudtrace1-cli-1.0.7+20171202 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 12:13:05.467 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/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 12:13:05.975 INFO [stdout] 50bd2fb3024ebbacdcdd6388c35685a857e60d4cceec0017dee6dbddb68881de
Nov 18 12:13:05.978 INFO running `"docker" "start" "-a" "50bd2fb3024ebbacdcdd6388c35685a857e60d4cceec0017dee6dbddb68881de"`
Nov 18 12:13:07.580 INFO [stderr] usermod: no changes
Nov 18 12:13:07.627 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:13:07.627 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:13:07.628 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:13:07.628 INFO [stderr] files will be included as a binary target:
Nov 18 12:13:07.628 INFO [stderr] 
Nov 18 12:13:07.629 INFO [stderr] * /source/src/main.rs
Nov 18 12:13:07.629 INFO [stderr] 
Nov 18 12:13:07.629 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:13:07.629 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:13:07.630 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:13:07.630 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:13:07.630 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:13:07.630 INFO [stderr] 
Nov 18 12:13:07.631 INFO [stderr] For more information on this warning you can consult
Nov 18 12:13:07.631 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:13:07.631 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `cloudtrace1`,
Nov 18 12:13:07.632 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:13:07.863 INFO [stderr]    Compiling google-cloudtrace1 v1.0.8+20181004
Nov 18 12:13:13.027 INFO [stderr]    Compiling google-cloudtrace1-cli v1.0.7+20171202 (/source)
Nov 18 12:13:27.292 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 19.69s
Nov 18 12:13:27.305 INFO [stderr] su: No module specific data is present
Nov 18 12:13:28.975 INFO running `"docker" "inspect" "50bd2fb3024ebbacdcdd6388c35685a857e60d4cceec0017dee6dbddb68881de"`
Nov 18 12:13:29.315 INFO running `"docker" "rm" "-f" "50bd2fb3024ebbacdcdd6388c35685a857e60d4cceec0017dee6dbddb68881de"`
Nov 18 12:13:29.675 INFO [stdout] 50bd2fb3024ebbacdcdd6388c35685a857e60d4cceec0017dee6dbddb68881de
Nov 18 12:13:29.683 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/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 12:13:30.129 INFO [stdout] e967ef22ebfa115c379777f75a0a1ffadb97194b4ffb848ccf7dc5b3869fbec0
Nov 18 12:13:30.130 INFO running `"docker" "start" "-a" "e967ef22ebfa115c379777f75a0a1ffadb97194b4ffb848ccf7dc5b3869fbec0"`
Nov 18 12:13:31.390 INFO [stderr] usermod: no changes
Nov 18 12:13:31.423 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:13:31.423 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:13:31.423 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:13:31.423 INFO [stderr] files will be included as a binary target:
Nov 18 12:13:31.423 INFO [stderr] 
Nov 18 12:13:31.423 INFO [stderr] * /source/src/main.rs
Nov 18 12:13:31.423 INFO [stderr] 
Nov 18 12:13:31.423 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:13:31.423 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:13:31.423 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:13:31.423 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:13:31.423 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:13:31.423 INFO [stderr] 
Nov 18 12:13:31.423 INFO [stderr] For more information on this warning you can consult
Nov 18 12:13:31.423 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:13:31.423 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `cloudtrace1`,
Nov 18 12:13:31.423 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:13:31.571 INFO [stderr]    Compiling google-cloudtrace1-cli v1.0.7+20171202 (/source)
Nov 18 12:13:37.223 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.81s
Nov 18 12:13:37.231 INFO [stderr] su: No module specific data is present
Nov 18 12:13:37.973 INFO running `"docker" "inspect" "e967ef22ebfa115c379777f75a0a1ffadb97194b4ffb848ccf7dc5b3869fbec0"`
Nov 18 12:13:38.167 INFO running `"docker" "rm" "-f" "e967ef22ebfa115c379777f75a0a1ffadb97194b4ffb848ccf7dc5b3869fbec0"`
Nov 18 12:13:38.590 INFO [stdout] e967ef22ebfa115c379777f75a0a1ffadb97194b4ffb848ccf7dc5b3869fbec0
Nov 18 12:13:38.597 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/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 12:13:38.943 INFO [stdout] 383b0bfaa333ed18d7998968ff682dc6d69c0e3911cb7d2586f30b33db35cc11
Nov 18 12:13:38.946 INFO running `"docker" "start" "-a" "383b0bfaa333ed18d7998968ff682dc6d69c0e3911cb7d2586f30b33db35cc11"`
Nov 18 12:13:40.075 INFO [stderr] usermod: no changes
Nov 18 12:13:40.115 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:13:40.115 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:13:40.115 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:13:40.115 INFO [stderr] files will be included as a binary target:
Nov 18 12:13:40.115 INFO [stderr] 
Nov 18 12:13:40.115 INFO [stderr] * /source/src/main.rs
Nov 18 12:13:40.115 INFO [stderr] 
Nov 18 12:13:40.115 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:13:40.115 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:13:40.115 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:13:40.115 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:13:40.115 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:13:40.115 INFO [stderr] 
Nov 18 12:13:40.115 INFO [stderr] For more information on this warning you can consult
Nov 18 12:13:40.115 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:13:40.115 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `cloudtrace1`,
Nov 18 12:13:40.115 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:13:40.279 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.17s
Nov 18 12:13:40.291 INFO [stderr]      Running /target/debug/deps/cloudtrace1-13ff63cf16f8f7b1
Nov 18 12:13:40.293 INFO [stdout] 
Nov 18 12:13:40.293 INFO [stdout] running 0 tests
Nov 18 12:13:40.294 INFO [stdout] 
Nov 18 12:13:40.294 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:13:40.294 INFO [stdout] 
Nov 18 12:13:40.304 INFO [stderr] su: No module specific data is present
Nov 18 12:13:40.793 INFO running `"docker" "inspect" "383b0bfaa333ed18d7998968ff682dc6d69c0e3911cb7d2586f30b33db35cc11"`
Nov 18 12:13:41.059 INFO running `"docker" "rm" "-f" "383b0bfaa333ed18d7998968ff682dc6d69c0e3911cb7d2586f30b33db35cc11"`
Nov 18 12:13:41.375 INFO [stdout] 383b0bfaa333ed18d7998968ff682dc6d69c0e3911cb7d2586f30b33db35cc11