Nov 18 10:34:44.964 INFO testing google-testing1-cli-1.0.7+20171201 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 10:34:44.965 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 10:34:45.317 INFO [stdout] dc4388202aa950a6d4f795203df7d2e1ef3f89f7b672348c8b4b9720739f0757
Nov 18 10:34:45.319 INFO running `"docker" "start" "-a" "dc4388202aa950a6d4f795203df7d2e1ef3f89f7b672348c8b4b9720739f0757"`
Nov 18 10:34:47.434 INFO [stderr] usermod: no changes
Nov 18 10:34:47.523 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:34:47.523 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:34:47.523 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:34:47.523 INFO [stderr] files will be included as a binary target:
Nov 18 10:34:47.523 INFO [stderr] 
Nov 18 10:34:47.523 INFO [stderr] * /source/src/main.rs
Nov 18 10:34:47.523 INFO [stderr] 
Nov 18 10:34:47.523 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:34:47.523 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:34:47.523 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:34:47.523 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:34:47.523 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:34:47.523 INFO [stderr] 
Nov 18 10:34:47.523 INFO [stderr] For more information on this warning you can consult
Nov 18 10:34:47.523 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:34:47.523 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `testing1`,
Nov 18 10:34:47.523 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:34:47.808 INFO [stderr]    Compiling google-testing1 v1.0.8+20181011
Nov 18 10:34:58.107 INFO [stderr]    Compiling google-testing1-cli v1.0.7+20171201 (/source)
Nov 18 10:35:20.955 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 33.50s
Nov 18 10:35:20.971 INFO [stderr] su: No module specific data is present
Nov 18 10:35:21.875 INFO running `"docker" "inspect" "dc4388202aa950a6d4f795203df7d2e1ef3f89f7b672348c8b4b9720739f0757"`
Nov 18 10:35:22.159 INFO running `"docker" "rm" "-f" "dc4388202aa950a6d4f795203df7d2e1ef3f89f7b672348c8b4b9720739f0757"`
Nov 18 10:35:22.611 INFO [stdout] dc4388202aa950a6d4f795203df7d2e1ef3f89f7b672348c8b4b9720739f0757
Nov 18 10:35:22.618 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 10:35:23.097 INFO [stdout] 5f59f8ac6cb6a46ef46a6ce9918675ae8a1d70c050f844ef919fb13bcab631b3
Nov 18 10:35:23.099 INFO running `"docker" "start" "-a" "5f59f8ac6cb6a46ef46a6ce9918675ae8a1d70c050f844ef919fb13bcab631b3"`
Nov 18 10:35:24.511 INFO [stderr] usermod: no changes
Nov 18 10:35:24.571 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:35:24.571 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:35:24.572 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:35:24.572 INFO [stderr] files will be included as a binary target:
Nov 18 10:35:24.572 INFO [stderr] 
Nov 18 10:35:24.573 INFO [stderr] * /source/src/main.rs
Nov 18 10:35:24.573 INFO [stderr] 
Nov 18 10:35:24.573 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:35:24.573 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:35:24.574 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:35:24.574 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:35:24.574 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:35:24.574 INFO [stderr] 
Nov 18 10:35:24.575 INFO [stderr] For more information on this warning you can consult
Nov 18 10:35:24.575 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:35:24.575 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `testing1`,
Nov 18 10:35:24.576 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:35:24.795 INFO [stderr]    Compiling google-testing1-cli v1.0.7+20171201 (/source)
Nov 18 10:35:30.975 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.43s
Nov 18 10:35:30.991 INFO [stderr] su: No module specific data is present
Nov 18 10:35:32.099 INFO running `"docker" "inspect" "5f59f8ac6cb6a46ef46a6ce9918675ae8a1d70c050f844ef919fb13bcab631b3"`
Nov 18 10:35:32.399 INFO running `"docker" "rm" "-f" "5f59f8ac6cb6a46ef46a6ce9918675ae8a1d70c050f844ef919fb13bcab631b3"`
Nov 18 10:35:32.790 INFO [stdout] 5f59f8ac6cb6a46ef46a6ce9918675ae8a1d70c050f844ef919fb13bcab631b3
Nov 18 10:35:32.796 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 10:35:33.388 INFO [stdout] 66f0b570a8e2f41adc391aded815227e7e494d2fba5f63739746e6761015a398
Nov 18 10:35:33.390 INFO running `"docker" "start" "-a" "66f0b570a8e2f41adc391aded815227e7e494d2fba5f63739746e6761015a398"`
Nov 18 10:35:34.941 INFO [stderr] usermod: no changes
Nov 18 10:35:35.003 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:35:35.004 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:35:35.004 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:35:35.004 INFO [stderr] files will be included as a binary target:
Nov 18 10:35:35.004 INFO [stderr] 
Nov 18 10:35:35.005 INFO [stderr] * /source/src/main.rs
Nov 18 10:35:35.005 INFO [stderr] 
Nov 18 10:35:35.005 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:35:35.006 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:35:35.006 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:35:35.006 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:35:35.007 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:35:35.007 INFO [stderr] 
Nov 18 10:35:35.007 INFO [stderr] For more information on this warning you can consult
Nov 18 10:35:35.007 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:35:35.008 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `testing1`,
Nov 18 10:35:35.008 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:35:35.203 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.23s
Nov 18 10:35:35.234 INFO [stderr]      Running /target/debug/deps/testing1-491a45f9e0335060
Nov 18 10:35:35.237 INFO [stdout] 
Nov 18 10:35:35.237 INFO [stdout] running 0 tests
Nov 18 10:35:35.237 INFO [stdout] 
Nov 18 10:35:35.237 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:35:35.237 INFO [stdout] 
Nov 18 10:35:35.245 INFO [stderr] su: No module specific data is present
Nov 18 10:35:36.287 INFO running `"docker" "inspect" "66f0b570a8e2f41adc391aded815227e7e494d2fba5f63739746e6761015a398"`
Nov 18 10:35:36.568 INFO running `"docker" "rm" "-f" "66f0b570a8e2f41adc391aded815227e7e494d2fba5f63739746e6761015a398"`
Nov 18 10:35:36.861 INFO [stdout] 66f0b570a8e2f41adc391aded815227e7e494d2fba5f63739746e6761015a398