Nov 18 10:50:06.055 INFO testing google-safebrowsing4-cli-1.0.7+20171204 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 10:50:06.055 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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:50:06.427 INFO [stdout] 9ea7c672ba043d8a8b9b18808d166103ca69cf76969a3f5cabd6ae66dcd14757
Nov 18 10:50:06.429 INFO running `"docker" "start" "-a" "9ea7c672ba043d8a8b9b18808d166103ca69cf76969a3f5cabd6ae66dcd14757"`
Nov 18 10:50:08.246 INFO [stderr] usermod: no changes
Nov 18 10:50:08.291 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:50:08.292 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:50:08.292 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:50:08.292 INFO [stderr] files will be included as a binary target:
Nov 18 10:50:08.293 INFO [stderr] 
Nov 18 10:50:08.293 INFO [stderr] * /source/src/main.rs
Nov 18 10:50:08.293 INFO [stderr] 
Nov 18 10:50:08.294 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:50:08.294 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:50:08.294 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:50:08.295 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:50:08.295 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:50:08.295 INFO [stderr] 
Nov 18 10:50:08.295 INFO [stderr] For more information on this warning you can consult
Nov 18 10:50:08.296 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:50:08.296 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `safebrowsing4`,
Nov 18 10:50:08.296 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:50:08.475 INFO [stderr]    Compiling google-safebrowsing4 v1.0.8+20181010
Nov 18 10:50:15.415 INFO [stderr]    Compiling google-safebrowsing4-cli v1.0.7+20171204 (/source)
Nov 18 10:50:29.679 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 21.41s
Nov 18 10:50:29.695 INFO [stderr] su: No module specific data is present
Nov 18 10:50:31.341 INFO running `"docker" "inspect" "9ea7c672ba043d8a8b9b18808d166103ca69cf76969a3f5cabd6ae66dcd14757"`
Nov 18 10:50:31.731 INFO running `"docker" "rm" "-f" "9ea7c672ba043d8a8b9b18808d166103ca69cf76969a3f5cabd6ae66dcd14757"`
Nov 18 10:50:32.123 INFO [stdout] 9ea7c672ba043d8a8b9b18808d166103ca69cf76969a3f5cabd6ae66dcd14757
Nov 18 10:50:32.126 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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:50:32.583 INFO [stdout] 0296e9345e3026c1b6c40e2d8508d7e9e3fb0c4d8c445508fbb1d7e6c0653e7f
Nov 18 10:50:32.589 INFO running `"docker" "start" "-a" "0296e9345e3026c1b6c40e2d8508d7e9e3fb0c4d8c445508fbb1d7e6c0653e7f"`
Nov 18 10:50:33.879 INFO [stderr] usermod: no changes
Nov 18 10:50:33.958 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:50:33.958 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:50:33.958 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:50:33.958 INFO [stderr] files will be included as a binary target:
Nov 18 10:50:33.958 INFO [stderr] 
Nov 18 10:50:33.958 INFO [stderr] * /source/src/main.rs
Nov 18 10:50:33.958 INFO [stderr] 
Nov 18 10:50:33.958 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:50:33.958 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:50:33.958 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:50:33.958 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:50:33.958 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:50:33.958 INFO [stderr] 
Nov 18 10:50:33.958 INFO [stderr] For more information on this warning you can consult
Nov 18 10:50:33.958 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:50:33.958 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `safebrowsing4`,
Nov 18 10:50:33.958 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:50:34.175 INFO [stderr]    Compiling google-safebrowsing4-cli v1.0.7+20171204 (/source)
Nov 18 10:50:40.090 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.18s
Nov 18 10:50:40.107 INFO [stderr] su: No module specific data is present
Nov 18 10:50:40.859 INFO running `"docker" "inspect" "0296e9345e3026c1b6c40e2d8508d7e9e3fb0c4d8c445508fbb1d7e6c0653e7f"`
Nov 18 10:50:41.162 INFO running `"docker" "rm" "-f" "0296e9345e3026c1b6c40e2d8508d7e9e3fb0c4d8c445508fbb1d7e6c0653e7f"`
Nov 18 10:50:41.416 INFO [stdout] 0296e9345e3026c1b6c40e2d8508d7e9e3fb0c4d8c445508fbb1d7e6c0653e7f
Nov 18 10:50:41.425 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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:50:41.771 INFO [stdout] 04010a0d1011d66bf92e90059641e06c0f7bbf025b0bb3ebb5be23bb5be0f1f3
Nov 18 10:50:41.779 INFO running `"docker" "start" "-a" "04010a0d1011d66bf92e90059641e06c0f7bbf025b0bb3ebb5be23bb5be0f1f3"`
Nov 18 10:50:42.599 INFO [stderr] usermod: no changes
Nov 18 10:50:42.639 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:50:42.639 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:50:42.639 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:50:42.639 INFO [stderr] files will be included as a binary target:
Nov 18 10:50:42.639 INFO [stderr] 
Nov 18 10:50:42.639 INFO [stderr] * /source/src/main.rs
Nov 18 10:50:42.639 INFO [stderr] 
Nov 18 10:50:42.639 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:50:42.639 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:50:42.639 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:50:42.639 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:50:42.639 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:50:42.639 INFO [stderr] 
Nov 18 10:50:42.639 INFO [stderr] For more information on this warning you can consult
Nov 18 10:50:42.639 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:50:42.639 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `safebrowsing4`,
Nov 18 10:50:42.639 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:50:42.774 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.14s
Nov 18 10:50:42.792 INFO [stderr]      Running /target/debug/deps/safebrowsing4-4f9e2c4805b93031
Nov 18 10:50:42.792 INFO [stdout] 
Nov 18 10:50:42.792 INFO [stdout] running 0 tests
Nov 18 10:50:42.795 INFO [stdout] 
Nov 18 10:50:42.795 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:50:42.795 INFO [stdout] 
Nov 18 10:50:42.797 INFO [stderr] su: No module specific data is present
Nov 18 10:50:43.407 INFO running `"docker" "inspect" "04010a0d1011d66bf92e90059641e06c0f7bbf025b0bb3ebb5be23bb5be0f1f3"`
Nov 18 10:50:43.659 INFO running `"docker" "rm" "-f" "04010a0d1011d66bf92e90059641e06c0f7bbf025b0bb3ebb5be23bb5be0f1f3"`
Nov 18 10:50:43.847 INFO [stdout] 04010a0d1011d66bf92e90059641e06c0f7bbf025b0bb3ebb5be23bb5be0f1f3