Nov 18 12:03:06.440 INFO testing google-content2-cli-1.0.7+20171207 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 12:03:06.440 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:03:06.912 INFO [stdout] fcb9412b911a383b73be5624b84bc2fa070421da03de454c5af867cb71eee026
Nov 18 12:03:06.914 INFO running `"docker" "start" "-a" "fcb9412b911a383b73be5624b84bc2fa070421da03de454c5af867cb71eee026"`
Nov 18 12:03:08.677 INFO [stderr] usermod: no changes
Nov 18 12:03:08.711 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:03:08.711 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:03:08.711 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:03:08.711 INFO [stderr] files will be included as a binary target:
Nov 18 12:03:08.711 INFO [stderr] 
Nov 18 12:03:08.711 INFO [stderr] * /source/src/main.rs
Nov 18 12:03:08.711 INFO [stderr] 
Nov 18 12:03:08.711 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:03:08.711 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:03:08.711 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:03:08.711 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:03:08.711 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:03:08.711 INFO [stderr] 
Nov 18 12:03:08.711 INFO [stderr] For more information on this warning you can consult
Nov 18 12:03:08.711 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:03:08.711 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `content2`,
Nov 18 12:03:08.711 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:03:09.007 INFO [stderr]    Compiling google-content2 v1.0.8+20181009
Nov 18 12:03:45.436 INFO [stderr]    Compiling google-content2-cli v1.0.7+20171207 (/source)
Nov 18 12:04:45.799 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1m 37s
Nov 18 12:04:45.825 INFO [stderr] su: No module specific data is present
Nov 18 12:04:46.385 INFO running `"docker" "inspect" "fcb9412b911a383b73be5624b84bc2fa070421da03de454c5af867cb71eee026"`
Nov 18 12:04:46.683 INFO running `"docker" "rm" "-f" "fcb9412b911a383b73be5624b84bc2fa070421da03de454c5af867cb71eee026"`
Nov 18 12:04:47.011 INFO [stdout] fcb9412b911a383b73be5624b84bc2fa070421da03de454c5af867cb71eee026
Nov 18 12:04:47.018 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:04:47.419 INFO [stdout] f3f81e03c367d754cc447f0e9cc25062b50649c522f37304e75ca2096ca6d839
Nov 18 12:04:47.421 INFO running `"docker" "start" "-a" "f3f81e03c367d754cc447f0e9cc25062b50649c522f37304e75ca2096ca6d839"`
Nov 18 12:04:49.205 INFO [stderr] usermod: no changes
Nov 18 12:04:49.249 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:04:49.249 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:04:49.249 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:04:49.249 INFO [stderr] files will be included as a binary target:
Nov 18 12:04:49.249 INFO [stderr] 
Nov 18 12:04:49.249 INFO [stderr] * /source/src/main.rs
Nov 18 12:04:49.249 INFO [stderr] 
Nov 18 12:04:49.249 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:04:49.249 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:04:49.249 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:04:49.249 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:04:49.249 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:04:49.249 INFO [stderr] 
Nov 18 12:04:49.249 INFO [stderr] For more information on this warning you can consult
Nov 18 12:04:49.249 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:04:49.249 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `content2`,
Nov 18 12:04:49.249 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:04:49.504 INFO [stderr]    Compiling google-content2-cli v1.0.7+20171207 (/source)
Nov 18 12:04:57.083 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 7.85s
Nov 18 12:04:57.091 INFO [stderr] su: No module specific data is present
Nov 18 12:04:58.035 INFO running `"docker" "inspect" "f3f81e03c367d754cc447f0e9cc25062b50649c522f37304e75ca2096ca6d839"`
Nov 18 12:04:58.415 INFO running `"docker" "rm" "-f" "f3f81e03c367d754cc447f0e9cc25062b50649c522f37304e75ca2096ca6d839"`
Nov 18 12:04:58.698 INFO [stdout] f3f81e03c367d754cc447f0e9cc25062b50649c522f37304e75ca2096ca6d839
Nov 18 12:04:58.702 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:04:59.200 INFO [stdout] 331e0094a71f364426879522041df101fa9f2d471f0fae35d57849cf9e579ab5
Nov 18 12:04:59.203 INFO running `"docker" "start" "-a" "331e0094a71f364426879522041df101fa9f2d471f0fae35d57849cf9e579ab5"`
Nov 18 12:05:01.430 INFO [stderr] usermod: no changes
Nov 18 12:05:01.483 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:05:01.483 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:05:01.483 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:05:01.483 INFO [stderr] files will be included as a binary target:
Nov 18 12:05:01.483 INFO [stderr] 
Nov 18 12:05:01.483 INFO [stderr] * /source/src/main.rs
Nov 18 12:05:01.483 INFO [stderr] 
Nov 18 12:05:01.483 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:05:01.483 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:05:01.483 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:05:01.483 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:05:01.483 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:05:01.483 INFO [stderr] 
Nov 18 12:05:01.483 INFO [stderr] For more information on this warning you can consult
Nov 18 12:05:01.483 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:05:01.483 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `content2`,
Nov 18 12:05:01.483 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:05:01.681 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.22s
Nov 18 12:05:01.696 INFO [stderr]      Running /target/debug/deps/content2-ad8fa041d6e4e637
Nov 18 12:05:01.701 INFO [stdout] 
Nov 18 12:05:01.701 INFO [stdout] running 0 tests
Nov 18 12:05:01.701 INFO [stdout] 
Nov 18 12:05:01.701 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:05:01.701 INFO [stdout] 
Nov 18 12:05:01.704 INFO [stderr] su: No module specific data is present
Nov 18 12:05:02.831 INFO running `"docker" "inspect" "331e0094a71f364426879522041df101fa9f2d471f0fae35d57849cf9e579ab5"`
Nov 18 12:05:03.053 INFO running `"docker" "rm" "-f" "331e0094a71f364426879522041df101fa9f2d471f0fae35d57849cf9e579ab5"`
Nov 18 12:05:03.390 INFO [stdout] 331e0094a71f364426879522041df101fa9f2d471f0fae35d57849cf9e579ab5