Nov 18 12:05:03.463 INFO testing google-container1-cli-1.0.7+20171111 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 12:05:03.464 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 12:05:03.857 INFO [stdout] 6c20f9e4050636e275e891cf2af5254bf7f766b27e0cdcdb504a9fc233bf37fc
Nov 18 12:05:03.859 INFO running `"docker" "start" "-a" "6c20f9e4050636e275e891cf2af5254bf7f766b27e0cdcdb504a9fc233bf37fc"`
Nov 18 12:05:05.886 INFO [stderr] usermod: no changes
Nov 18 12:05:05.921 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:05:05.921 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:05:05.921 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:05:05.921 INFO [stderr] files will be included as a binary target:
Nov 18 12:05:05.921 INFO [stderr] 
Nov 18 12:05:05.921 INFO [stderr] * /source/src/main.rs
Nov 18 12:05:05.921 INFO [stderr] 
Nov 18 12:05:05.921 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:05:05.921 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:05:05.922 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:05:05.922 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:05:05.922 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:05:05.922 INFO [stderr] 
Nov 18 12:05:05.922 INFO [stderr] For more information on this warning you can consult
Nov 18 12:05:05.922 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:05:05.922 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `container1`,
Nov 18 12:05:05.922 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:05:06.070 INFO [stderr]    Compiling google-container1 v1.0.8+20180917
Nov 18 12:05:19.519 INFO [stderr]    Compiling google-container1-cli v1.0.7+20171111 (/source)
Nov 18 12:05:46.569 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 40.65s
Nov 18 12:05:46.581 INFO [stderr] su: No module specific data is present
Nov 18 12:05:47.441 INFO running `"docker" "inspect" "6c20f9e4050636e275e891cf2af5254bf7f766b27e0cdcdb504a9fc233bf37fc"`
Nov 18 12:05:47.727 INFO running `"docker" "rm" "-f" "6c20f9e4050636e275e891cf2af5254bf7f766b27e0cdcdb504a9fc233bf37fc"`
Nov 18 12:05:47.967 INFO [stdout] 6c20f9e4050636e275e891cf2af5254bf7f766b27e0cdcdb504a9fc233bf37fc
Nov 18 12:05:47.971 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 12:05:48.379 INFO [stdout] 6e1ff27f0319a847a562fe46f55c1eaba6a55954b3cf0c466aaa76093bff00b3
Nov 18 12:05:48.382 INFO running `"docker" "start" "-a" "6e1ff27f0319a847a562fe46f55c1eaba6a55954b3cf0c466aaa76093bff00b3"`
Nov 18 12:05:49.793 INFO [stderr] usermod: no changes
Nov 18 12:05:49.863 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:05:49.863 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:05:49.863 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:05:49.863 INFO [stderr] files will be included as a binary target:
Nov 18 12:05:49.863 INFO [stderr] 
Nov 18 12:05:49.863 INFO [stderr] * /source/src/main.rs
Nov 18 12:05:49.863 INFO [stderr] 
Nov 18 12:05:49.863 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:05:49.863 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:05:49.863 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:05:49.863 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:05:49.863 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:05:49.863 INFO [stderr] 
Nov 18 12:05:49.863 INFO [stderr] For more information on this warning you can consult
Nov 18 12:05:49.863 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:05:49.863 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `container1`,
Nov 18 12:05:49.863 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:05:50.136 INFO [stderr]    Compiling google-container1-cli v1.0.7+20171111 (/source)
Nov 18 12:05:57.143 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 7.30s
Nov 18 12:05:57.155 INFO [stderr] su: No module specific data is present
Nov 18 12:05:58.217 INFO running `"docker" "inspect" "6e1ff27f0319a847a562fe46f55c1eaba6a55954b3cf0c466aaa76093bff00b3"`
Nov 18 12:05:58.440 INFO running `"docker" "rm" "-f" "6e1ff27f0319a847a562fe46f55c1eaba6a55954b3cf0c466aaa76093bff00b3"`
Nov 18 12:05:58.807 INFO [stdout] 6e1ff27f0319a847a562fe46f55c1eaba6a55954b3cf0c466aaa76093bff00b3
Nov 18 12:05:58.817 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 12:05:59.300 INFO [stdout] 460bc6a80b1f80dc10663d965c34f4b4ee4fab0458f57d8c41c1b96f05257879
Nov 18 12:05:59.302 INFO running `"docker" "start" "-a" "460bc6a80b1f80dc10663d965c34f4b4ee4fab0458f57d8c41c1b96f05257879"`
Nov 18 12:06:01.231 INFO [stderr] usermod: no changes
Nov 18 12:06:01.303 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:06:01.303 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:06:01.303 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:06:01.303 INFO [stderr] files will be included as a binary target:
Nov 18 12:06:01.303 INFO [stderr] 
Nov 18 12:06:01.303 INFO [stderr] * /source/src/main.rs
Nov 18 12:06:01.303 INFO [stderr] 
Nov 18 12:06:01.303 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:06:01.303 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:06:01.303 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:06:01.303 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:06:01.303 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:06:01.303 INFO [stderr] 
Nov 18 12:06:01.303 INFO [stderr] For more information on this warning you can consult
Nov 18 12:06:01.303 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:06:01.303 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `container1`,
Nov 18 12:06:01.303 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:06:01.557 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.28s
Nov 18 12:06:01.578 INFO [stderr]      Running /target/debug/deps/container1-efe1a6f2390b442e
Nov 18 12:06:01.580 INFO [stdout] 
Nov 18 12:06:01.581 INFO [stdout] running 0 tests
Nov 18 12:06:01.581 INFO [stdout] 
Nov 18 12:06:01.581 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:06:01.582 INFO [stdout] 
Nov 18 12:06:01.587 INFO [stderr] su: No module specific data is present
Nov 18 12:06:02.320 INFO running `"docker" "inspect" "460bc6a80b1f80dc10663d965c34f4b4ee4fab0458f57d8c41c1b96f05257879"`
Nov 18 12:06:02.733 INFO running `"docker" "rm" "-f" "460bc6a80b1f80dc10663d965c34f4b4ee4fab0458f57d8c41c1b96f05257879"`
Nov 18 12:06:03.107 INFO [stdout] 460bc6a80b1f80dc10663d965c34f4b4ee4fab0458f57d8c41c1b96f05257879