Nov 18 11:22:45.334 INFO testing google-discovery1-cli-1.0.7+00000000 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 11:22:45.335 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 11:22:45.899 INFO [stdout] c9ed9ea267cec856451eb78de0f7529402cdfb8957353698b70af35d55c53b13
Nov 18 11:22:45.901 INFO running `"docker" "start" "-a" "c9ed9ea267cec856451eb78de0f7529402cdfb8957353698b70af35d55c53b13"`
Nov 18 11:22:48.470 INFO [stderr] usermod: no changes
Nov 18 11:22:48.511 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 11:22:48.511 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 11:22:48.511 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 11:22:48.511 INFO [stderr] files will be included as a binary target:
Nov 18 11:22:48.511 INFO [stderr] 
Nov 18 11:22:48.511 INFO [stderr] * /source/src/main.rs
Nov 18 11:22:48.511 INFO [stderr] 
Nov 18 11:22:48.511 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 11:22:48.511 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 11:22:48.511 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 11:22:48.511 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 11:22:48.511 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 11:22:48.511 INFO [stderr] 
Nov 18 11:22:48.511 INFO [stderr] For more information on this warning you can consult
Nov 18 11:22:48.511 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 11:22:48.511 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `discovery1`,
Nov 18 11:22:48.511 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 11:22:48.739 INFO [stderr]    Compiling google-discovery1 v1.0.8+20181009
Nov 18 11:22:55.999 INFO [stderr]    Compiling google-discovery1-cli v1.0.7+00000000 (/source)
Nov 18 11:23:10.036 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 21.53s
Nov 18 11:23:10.045 INFO [stderr] su: No module specific data is present
Nov 18 11:23:10.525 INFO running `"docker" "inspect" "c9ed9ea267cec856451eb78de0f7529402cdfb8957353698b70af35d55c53b13"`
Nov 18 11:23:10.795 INFO running `"docker" "rm" "-f" "c9ed9ea267cec856451eb78de0f7529402cdfb8957353698b70af35d55c53b13"`
Nov 18 11:23:11.064 INFO [stdout] c9ed9ea267cec856451eb78de0f7529402cdfb8957353698b70af35d55c53b13
Nov 18 11:23:11.072 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 11:23:11.466 INFO [stdout] 1ae9e35c998b34e2a5f8b7c327472783798bf70ffe6928830126ec93a31cc42e
Nov 18 11:23:11.468 INFO running `"docker" "start" "-a" "1ae9e35c998b34e2a5f8b7c327472783798bf70ffe6928830126ec93a31cc42e"`
Nov 18 11:23:12.391 INFO [stderr] usermod: no changes
Nov 18 11:23:12.467 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 11:23:12.467 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 11:23:12.467 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 11:23:12.467 INFO [stderr] files will be included as a binary target:
Nov 18 11:23:12.467 INFO [stderr] 
Nov 18 11:23:12.467 INFO [stderr] * /source/src/main.rs
Nov 18 11:23:12.467 INFO [stderr] 
Nov 18 11:23:12.467 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 11:23:12.467 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 11:23:12.467 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 11:23:12.467 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 11:23:12.467 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 11:23:12.467 INFO [stderr] 
Nov 18 11:23:12.467 INFO [stderr] For more information on this warning you can consult
Nov 18 11:23:12.467 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 11:23:12.467 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `discovery1`,
Nov 18 11:23:12.467 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 11:23:12.675 INFO [stderr]    Compiling google-discovery1-cli v1.0.7+00000000 (/source)
Nov 18 11:23:18.403 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.98s
Nov 18 11:23:18.419 INFO [stderr] su: No module specific data is present
Nov 18 11:23:19.252 INFO running `"docker" "inspect" "1ae9e35c998b34e2a5f8b7c327472783798bf70ffe6928830126ec93a31cc42e"`
Nov 18 11:23:19.541 INFO running `"docker" "rm" "-f" "1ae9e35c998b34e2a5f8b7c327472783798bf70ffe6928830126ec93a31cc42e"`
Nov 18 11:23:19.811 INFO [stdout] 1ae9e35c998b34e2a5f8b7c327472783798bf70ffe6928830126ec93a31cc42e
Nov 18 11:23:19.816 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 11:23:20.231 INFO [stdout] 92c8f60329c509d76323f8531488832e3e1df2e1b86fda7c60229f4de515f2ae
Nov 18 11:23:20.239 INFO running `"docker" "start" "-a" "92c8f60329c509d76323f8531488832e3e1df2e1b86fda7c60229f4de515f2ae"`
Nov 18 11:23:21.746 INFO [stderr] usermod: no changes
Nov 18 11:23:21.803 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 11:23:21.803 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 11:23:21.803 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 11:23:21.803 INFO [stderr] files will be included as a binary target:
Nov 18 11:23:21.803 INFO [stderr] 
Nov 18 11:23:21.803 INFO [stderr] * /source/src/main.rs
Nov 18 11:23:21.803 INFO [stderr] 
Nov 18 11:23:21.803 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 11:23:21.803 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 11:23:21.803 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 11:23:21.803 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 11:23:21.803 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 11:23:21.803 INFO [stderr] 
Nov 18 11:23:21.803 INFO [stderr] For more information on this warning you can consult
Nov 18 11:23:21.803 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 11:23:21.803 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `discovery1`,
Nov 18 11:23:21.803 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 11:23:22.055 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.26s
Nov 18 11:23:22.055 INFO [stderr]      Running /target/debug/deps/discovery1-55ecc240017f2ed6
Nov 18 11:23:22.058 INFO [stdout] 
Nov 18 11:23:22.058 INFO [stdout] running 0 tests
Nov 18 11:23:22.066 INFO [stdout] 
Nov 18 11:23:22.066 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 11:23:22.066 INFO [stdout] 
Nov 18 11:23:22.067 INFO [stderr] su: No module specific data is present
Nov 18 11:23:23.244 INFO running `"docker" "inspect" "92c8f60329c509d76323f8531488832e3e1df2e1b86fda7c60229f4de515f2ae"`
Nov 18 11:23:23.631 INFO running `"docker" "rm" "-f" "92c8f60329c509d76323f8531488832e3e1df2e1b86fda7c60229f4de515f2ae"`
Nov 18 11:23:23.971 INFO [stdout] 92c8f60329c509d76323f8531488832e3e1df2e1b86fda7c60229f4de515f2ae