Nov 18 12:05:01.487 INFO testing google-container1-cli-1.0.7+20171111 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 12:05:01.487 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:05:02.112 INFO [stdout] b6676e491b7a7d3a33b683331b79d9d192e111888ee41934f7ca1e558eedd870
Nov 18 12:05:02.114 INFO running `"docker" "start" "-a" "b6676e491b7a7d3a33b683331b79d9d192e111888ee41934f7ca1e558eedd870"`
Nov 18 12:05:04.136 INFO [stderr] usermod: no changes
Nov 18 12:05:04.187 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:05:04.187 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:05:04.187 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:05:04.187 INFO [stderr] files will be included as a binary target:
Nov 18 12:05:04.187 INFO [stderr] 
Nov 18 12:05:04.187 INFO [stderr] * /source/src/main.rs
Nov 18 12:05:04.187 INFO [stderr] 
Nov 18 12:05:04.187 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:05:04.187 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:05:04.187 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:05:04.187 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:05:04.187 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:05:04.187 INFO [stderr] 
Nov 18 12:05:04.187 INFO [stderr] For more information on this warning you can consult
Nov 18 12:05:04.187 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:05:04.187 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `container1`,
Nov 18 12:05:04.187 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:05:04.371 INFO [stderr]    Compiling google-container1 v1.0.8+20180917
Nov 18 12:05:17.995 INFO [stderr]    Compiling google-container1-cli v1.0.7+20171111 (/source)
Nov 18 12:05:44.704 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 40.54s
Nov 18 12:05:44.719 INFO [stderr] su: No module specific data is present
Nov 18 12:05:46.188 INFO running `"docker" "inspect" "b6676e491b7a7d3a33b683331b79d9d192e111888ee41934f7ca1e558eedd870"`
Nov 18 12:05:46.497 INFO running `"docker" "rm" "-f" "b6676e491b7a7d3a33b683331b79d9d192e111888ee41934f7ca1e558eedd870"`
Nov 18 12:05:46.775 INFO [stdout] b6676e491b7a7d3a33b683331b79d9d192e111888ee41934f7ca1e558eedd870
Nov 18 12:05:46.785 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:05:47.293 INFO [stdout] 8918caf073cf40f0b6ac60eb7b3ddb6503cbe70b3dac51dac1ab2071602d4c2d
Nov 18 12:05:47.296 INFO running `"docker" "start" "-a" "8918caf073cf40f0b6ac60eb7b3ddb6503cbe70b3dac51dac1ab2071602d4c2d"`
Nov 18 12:05:48.567 INFO [stderr] usermod: no changes
Nov 18 12:05:48.619 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:05:48.619 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:05:48.619 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:05:48.619 INFO [stderr] files will be included as a binary target:
Nov 18 12:05:48.619 INFO [stderr] 
Nov 18 12:05:48.619 INFO [stderr] * /source/src/main.rs
Nov 18 12:05:48.619 INFO [stderr] 
Nov 18 12:05:48.619 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:05:48.619 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:05:48.619 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:05:48.619 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:05:48.619 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:05:48.619 INFO [stderr] 
Nov 18 12:05:48.619 INFO [stderr] For more information on this warning you can consult
Nov 18 12:05:48.619 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:05:48.620 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `container1`,
Nov 18 12:05:48.620 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:05:48.883 INFO [stderr]    Compiling google-container1-cli v1.0.7+20171111 (/source)
Nov 18 12:05:55.243 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.65s
Nov 18 12:05:55.259 INFO [stderr] su: No module specific data is present
Nov 18 12:05:56.156 INFO running `"docker" "inspect" "8918caf073cf40f0b6ac60eb7b3ddb6503cbe70b3dac51dac1ab2071602d4c2d"`
Nov 18 12:05:56.599 INFO running `"docker" "rm" "-f" "8918caf073cf40f0b6ac60eb7b3ddb6503cbe70b3dac51dac1ab2071602d4c2d"`
Nov 18 12:05:56.971 INFO [stdout] 8918caf073cf40f0b6ac60eb7b3ddb6503cbe70b3dac51dac1ab2071602d4c2d
Nov 18 12:05:56.978 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:05:57.532 INFO [stdout] c818725de76e7239e1b2f78fe3566b912d9bb9e915ade08ed738a5f876287165
Nov 18 12:05:57.535 INFO running `"docker" "start" "-a" "c818725de76e7239e1b2f78fe3566b912d9bb9e915ade08ed738a5f876287165"`
Nov 18 12:05:59.626 INFO [stderr] usermod: no changes
Nov 18 12:05:59.667 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:05:59.667 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:05:59.667 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:05:59.667 INFO [stderr] files will be included as a binary target:
Nov 18 12:05:59.667 INFO [stderr] 
Nov 18 12:05:59.667 INFO [stderr] * /source/src/main.rs
Nov 18 12:05:59.667 INFO [stderr] 
Nov 18 12:05:59.667 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:05:59.667 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:05:59.667 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:05:59.667 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:05:59.667 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:05:59.667 INFO [stderr] 
Nov 18 12:05:59.667 INFO [stderr] For more information on this warning you can consult
Nov 18 12:05:59.667 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:05:59.667 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `container1`,
Nov 18 12:05:59.667 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:05:59.871 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.22s
Nov 18 12:05:59.887 INFO [stdout] 
Nov 18 12:05:59.887 INFO [stdout] running 0 tests
Nov 18 12:05:59.887 INFO [stdout] 
Nov 18 12:05:59.887 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:05:59.887 INFO [stdout] 
Nov 18 12:05:59.888 INFO [stderr]      Running /target/debug/deps/container1-ca966dc8f21ecd7e
Nov 18 12:05:59.891 INFO [stderr] su: No module specific data is present
Nov 18 12:06:01.030 INFO running `"docker" "inspect" "c818725de76e7239e1b2f78fe3566b912d9bb9e915ade08ed738a5f876287165"`
Nov 18 12:06:01.331 INFO running `"docker" "rm" "-f" "c818725de76e7239e1b2f78fe3566b912d9bb9e915ade08ed738a5f876287165"`
Nov 18 12:06:01.663 INFO [stdout] c818725de76e7239e1b2f78fe3566b912d9bb9e915ade08ed738a5f876287165