Nov 18 10:49:22.996 INFO testing google-servicecontrol1-cli-1.0.7+20171202 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 10:49:22.996 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:49:23.219 INFO [stdout] 423baa1f81deba955436e8d3e612cbbf87f0658c643cc7cfd5f1fd92860a8b3b
Nov 18 10:49:23.222 INFO running `"docker" "start" "-a" "423baa1f81deba955436e8d3e612cbbf87f0658c643cc7cfd5f1fd92860a8b3b"`
Nov 18 10:49:23.741 INFO [stderr] usermod: no changes
Nov 18 10:49:23.782 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:49:23.783 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:49:23.783 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:49:23.783 INFO [stderr] files will be included as a binary target:
Nov 18 10:49:23.784 INFO [stderr] 
Nov 18 10:49:23.784 INFO [stderr] * /source/src/main.rs
Nov 18 10:49:23.784 INFO [stderr] 
Nov 18 10:49:23.784 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:49:23.784 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:49:23.785 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:49:23.785 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:49:23.785 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:49:23.785 INFO [stderr] 
Nov 18 10:49:23.786 INFO [stderr] For more information on this warning you can consult
Nov 18 10:49:23.786 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:49:23.786 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `servicecontrol1`,
Nov 18 10:49:23.786 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:49:23.975 INFO [stderr]    Compiling google-servicecontrol1 v1.0.8+20181008
Nov 18 10:49:29.750 INFO [stderr]    Compiling google-servicecontrol1-cli v1.0.7+20171202 (/source)
Nov 18 10:49:48.054 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 24.28s
Nov 18 10:49:48.083 INFO [stderr] su: No module specific data is present
Nov 18 10:49:48.795 INFO running `"docker" "inspect" "423baa1f81deba955436e8d3e612cbbf87f0658c643cc7cfd5f1fd92860a8b3b"`
Nov 18 10:49:49.003 INFO running `"docker" "rm" "-f" "423baa1f81deba955436e8d3e612cbbf87f0658c643cc7cfd5f1fd92860a8b3b"`
Nov 18 10:49:49.251 INFO [stdout] 423baa1f81deba955436e8d3e612cbbf87f0658c643cc7cfd5f1fd92860a8b3b
Nov 18 10:49:49.255 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:49:49.597 INFO [stdout] a598e34323a55e6ecee30c34ff75bfdf820775a4179ed9107d77d9132318fbe8
Nov 18 10:49:49.600 INFO running `"docker" "start" "-a" "a598e34323a55e6ecee30c34ff75bfdf820775a4179ed9107d77d9132318fbe8"`
Nov 18 10:49:50.531 INFO [stderr] usermod: no changes
Nov 18 10:49:50.562 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:49:50.562 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:49:50.562 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:49:50.562 INFO [stderr] files will be included as a binary target:
Nov 18 10:49:50.562 INFO [stderr] 
Nov 18 10:49:50.563 INFO [stderr] * /source/src/main.rs
Nov 18 10:49:50.563 INFO [stderr] 
Nov 18 10:49:50.563 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:49:50.563 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:49:50.563 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:49:50.563 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:49:50.563 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:49:50.563 INFO [stderr] 
Nov 18 10:49:50.563 INFO [stderr] For more information on this warning you can consult
Nov 18 10:49:50.563 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:49:50.563 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `servicecontrol1`,
Nov 18 10:49:50.563 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:49:50.699 INFO [stderr]    Compiling google-servicecontrol1-cli v1.0.7+20171202 (/source)
Nov 18 10:49:55.043 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 4.49s
Nov 18 10:49:55.059 INFO [stderr] su: No module specific data is present
Nov 18 10:49:56.183 INFO running `"docker" "inspect" "a598e34323a55e6ecee30c34ff75bfdf820775a4179ed9107d77d9132318fbe8"`
Nov 18 10:49:56.415 INFO running `"docker" "rm" "-f" "a598e34323a55e6ecee30c34ff75bfdf820775a4179ed9107d77d9132318fbe8"`
Nov 18 10:49:56.753 INFO [stdout] a598e34323a55e6ecee30c34ff75bfdf820775a4179ed9107d77d9132318fbe8
Nov 18 10:49:56.768 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-1/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:49:57.191 INFO [stdout] 6f4d6a67d33100dbb9e98337020d47ab639b5d956f61faad19dae3c92f853859
Nov 18 10:49:57.194 INFO running `"docker" "start" "-a" "6f4d6a67d33100dbb9e98337020d47ab639b5d956f61faad19dae3c92f853859"`
Nov 18 10:49:59.126 INFO [stderr] usermod: no changes
Nov 18 10:49:59.179 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:49:59.179 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:49:59.179 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:49:59.179 INFO [stderr] files will be included as a binary target:
Nov 18 10:49:59.179 INFO [stderr] 
Nov 18 10:49:59.179 INFO [stderr] * /source/src/main.rs
Nov 18 10:49:59.179 INFO [stderr] 
Nov 18 10:49:59.179 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:49:59.179 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:49:59.179 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:49:59.179 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:49:59.179 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:49:59.179 INFO [stderr] 
Nov 18 10:49:59.179 INFO [stderr] For more information on this warning you can consult
Nov 18 10:49:59.179 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:49:59.179 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `servicecontrol1`,
Nov 18 10:49:59.179 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:49:59.379 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.23s
Nov 18 10:49:59.401 INFO [stderr]      Running /target/debug/deps/servicecontrol1-f102da723222b1f2
Nov 18 10:49:59.406 INFO [stdout] 
Nov 18 10:49:59.406 INFO [stdout] running 0 tests
Nov 18 10:49:59.406 INFO [stdout] 
Nov 18 10:49:59.406 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:49:59.406 INFO [stdout] 
Nov 18 10:49:59.409 INFO [stderr] su: No module specific data is present
Nov 18 10:50:00.490 INFO running `"docker" "inspect" "6f4d6a67d33100dbb9e98337020d47ab639b5d956f61faad19dae3c92f853859"`
Nov 18 10:50:00.819 INFO running `"docker" "rm" "-f" "6f4d6a67d33100dbb9e98337020d47ab639b5d956f61faad19dae3c92f853859"`
Nov 18 10:50:01.187 INFO [stdout] 6f4d6a67d33100dbb9e98337020d47ab639b5d956f61faad19dae3c92f853859