Nov 18 10:55:03.440 INFO testing google-plus1-cli-1.0.7+20171030 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 10:55:03.440 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:55:03.989 INFO [stdout] 66b2cc07ed73ed48e82fb3a9e0528fa823bfc25116c37e5e2d22a98a103402e1
Nov 18 10:55:03.991 INFO running `"docker" "start" "-a" "66b2cc07ed73ed48e82fb3a9e0528fa823bfc25116c37e5e2d22a98a103402e1"`
Nov 18 10:55:05.342 INFO [stderr] usermod: no changes
Nov 18 10:55:05.415 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:55:05.415 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:55:05.415 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:55:05.415 INFO [stderr] files will be included as a binary target:
Nov 18 10:55:05.415 INFO [stderr] 
Nov 18 10:55:05.415 INFO [stderr] * /source/src/main.rs
Nov 18 10:55:05.415 INFO [stderr] 
Nov 18 10:55:05.415 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:55:05.415 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:55:05.415 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:55:05.415 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:55:05.415 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:55:05.415 INFO [stderr] 
Nov 18 10:55:05.415 INFO [stderr] For more information on this warning you can consult
Nov 18 10:55:05.415 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:55:05.415 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `plus1`,
Nov 18 10:55:05.415 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:55:05.599 INFO [stderr]    Compiling google-plus1 v1.0.8+20181007
Nov 18 10:55:15.559 INFO [stderr]    Compiling google-plus1-cli v1.0.7+20171030 (/source)
Nov 18 10:55:35.271 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 29.87s
Nov 18 10:55:35.283 INFO [stderr] su: No module specific data is present
Nov 18 10:55:36.130 INFO running `"docker" "inspect" "66b2cc07ed73ed48e82fb3a9e0528fa823bfc25116c37e5e2d22a98a103402e1"`
Nov 18 10:55:36.485 INFO running `"docker" "rm" "-f" "66b2cc07ed73ed48e82fb3a9e0528fa823bfc25116c37e5e2d22a98a103402e1"`
Nov 18 10:55:36.811 INFO [stdout] 66b2cc07ed73ed48e82fb3a9e0528fa823bfc25116c37e5e2d22a98a103402e1
Nov 18 10:55:36.813 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:55:37.251 INFO [stdout] 1ee64069666646c99968dc2cd44e9101020f2e5a810cfd7c79251da875e8bfed
Nov 18 10:55:37.255 INFO running `"docker" "start" "-a" "1ee64069666646c99968dc2cd44e9101020f2e5a810cfd7c79251da875e8bfed"`
Nov 18 10:55:38.295 INFO [stderr] usermod: no changes
Nov 18 10:55:38.359 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:55:38.359 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:55:38.359 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:55:38.359 INFO [stderr] files will be included as a binary target:
Nov 18 10:55:38.359 INFO [stderr] 
Nov 18 10:55:38.359 INFO [stderr] * /source/src/main.rs
Nov 18 10:55:38.359 INFO [stderr] 
Nov 18 10:55:38.359 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:55:38.359 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:55:38.359 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:55:38.359 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:55:38.359 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:55:38.359 INFO [stderr] 
Nov 18 10:55:38.359 INFO [stderr] For more information on this warning you can consult
Nov 18 10:55:38.359 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:55:38.359 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `plus1`,
Nov 18 10:55:38.359 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:55:38.571 INFO [stderr]    Compiling google-plus1-cli v1.0.7+20171030 (/source)
Nov 18 10:55:44.155 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.83s
Nov 18 10:55:44.175 INFO [stderr] su: No module specific data is present
Nov 18 10:55:44.879 INFO running `"docker" "inspect" "1ee64069666646c99968dc2cd44e9101020f2e5a810cfd7c79251da875e8bfed"`
Nov 18 10:55:45.149 INFO running `"docker" "rm" "-f" "1ee64069666646c99968dc2cd44e9101020f2e5a810cfd7c79251da875e8bfed"`
Nov 18 10:55:45.431 INFO [stdout] 1ee64069666646c99968dc2cd44e9101020f2e5a810cfd7c79251da875e8bfed
Nov 18 10:55:45.435 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:55:45.867 INFO [stdout] 07acda578a4666da93912454b9cefb53dea9d243a98373aa30c20bf664f9f4a2
Nov 18 10:55:45.873 INFO running `"docker" "start" "-a" "07acda578a4666da93912454b9cefb53dea9d243a98373aa30c20bf664f9f4a2"`
Nov 18 10:55:46.935 INFO [stderr] usermod: no changes
Nov 18 10:55:46.991 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:55:46.991 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:55:46.991 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:55:46.991 INFO [stderr] files will be included as a binary target:
Nov 18 10:55:46.991 INFO [stderr] 
Nov 18 10:55:46.991 INFO [stderr] * /source/src/main.rs
Nov 18 10:55:46.991 INFO [stderr] 
Nov 18 10:55:46.991 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:55:46.991 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:55:46.991 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:55:46.991 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:55:46.991 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:55:46.991 INFO [stderr] 
Nov 18 10:55:46.991 INFO [stderr] For more information on this warning you can consult
Nov 18 10:55:46.991 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:55:46.991 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `plus1`,
Nov 18 10:55:46.991 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:55:47.159 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.19s
Nov 18 10:55:47.173 INFO [stderr]      Running /target/debug/deps/plus1-d71364ac3480f5b9
Nov 18 10:55:47.187 INFO [stdout] 
Nov 18 10:55:47.187 INFO [stdout] running 0 tests
Nov 18 10:55:47.187 INFO [stdout] 
Nov 18 10:55:47.187 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:55:47.187 INFO [stdout] 
Nov 18 10:55:47.192 INFO [stderr] su: No module specific data is present
Nov 18 10:55:47.891 INFO running `"docker" "inspect" "07acda578a4666da93912454b9cefb53dea9d243a98373aa30c20bf664f9f4a2"`
Nov 18 10:55:48.161 INFO running `"docker" "rm" "-f" "07acda578a4666da93912454b9cefb53dea9d243a98373aa30c20bf664f9f4a2"`
Nov 18 10:55:48.450 INFO [stdout] 07acda578a4666da93912454b9cefb53dea9d243a98373aa30c20bf664f9f4a2