Nov 18 12:02:01.072 INFO testing google-content2_sandbox-cli-1.0.7+20171207 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 18 12:02:01.072 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 12:02:01.663 INFO [stdout] cdfe4048e300515e8d8d5440beb8fb8c9863e6677544d44b2f221cad7da6bebc Nov 18 12:02:01.667 INFO running `"docker" "start" "-a" "cdfe4048e300515e8d8d5440beb8fb8c9863e6677544d44b2f221cad7da6bebc"` Nov 18 12:02:02.974 INFO [stderr] usermod: no changes Nov 18 12:02:03.047 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 12:02:03.047 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 12:02:03.047 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 12:02:03.047 INFO [stderr] files will be included as a binary target: Nov 18 12:02:03.047 INFO [stderr] Nov 18 12:02:03.047 INFO [stderr] * /source/src/main.rs Nov 18 12:02:03.047 INFO [stderr] Nov 18 12:02:03.047 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 12:02:03.047 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 12:02:03.047 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 12:02:03.047 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 12:02:03.047 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 12:02:03.047 INFO [stderr] Nov 18 12:02:03.047 INFO [stderr] For more information on this warning you can consult Nov 18 12:02:03.047 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 12:02:03.047 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `content2-sandbox`, Nov 18 12:02:03.047 INFO [stderr] please set bin.path in Cargo.toml Nov 18 12:02:03.279 INFO [stderr] Compiling google-content2_sandbox v1.0.8+20181009 Nov 18 12:02:19.968 INFO [stderr] Compiling google-content2_sandbox-cli v1.0.7+20171207 (/source) Nov 18 12:02:47.491 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 44.49s Nov 18 12:02:47.510 INFO [stderr] su: No module specific data is present Nov 18 12:02:48.955 INFO running `"docker" "inspect" "cdfe4048e300515e8d8d5440beb8fb8c9863e6677544d44b2f221cad7da6bebc"` Nov 18 12:02:49.233 INFO running `"docker" "rm" "-f" "cdfe4048e300515e8d8d5440beb8fb8c9863e6677544d44b2f221cad7da6bebc"` Nov 18 12:02:49.622 INFO [stdout] cdfe4048e300515e8d8d5440beb8fb8c9863e6677544d44b2f221cad7da6bebc Nov 18 12:02:49.626 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 12:02:50.015 INFO [stdout] 41d34bb48bc5b359b53a4a42a197479fb37c71c0589ce4b8b3582c1d01d92917 Nov 18 12:02:50.018 INFO running `"docker" "start" "-a" "41d34bb48bc5b359b53a4a42a197479fb37c71c0589ce4b8b3582c1d01d92917"` Nov 18 12:02:51.567 INFO [stderr] usermod: no changes Nov 18 12:02:51.655 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 12:02:51.655 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 12:02:51.655 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 12:02:51.655 INFO [stderr] files will be included as a binary target: Nov 18 12:02:51.655 INFO [stderr] Nov 18 12:02:51.655 INFO [stderr] * /source/src/main.rs Nov 18 12:02:51.655 INFO [stderr] Nov 18 12:02:51.655 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 12:02:51.655 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 12:02:51.655 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 12:02:51.655 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 12:02:51.655 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 12:02:51.655 INFO [stderr] Nov 18 12:02:51.655 INFO [stderr] For more information on this warning you can consult Nov 18 12:02:51.655 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 12:02:51.655 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `content2-sandbox`, Nov 18 12:02:51.655 INFO [stderr] please set bin.path in Cargo.toml Nov 18 12:02:51.849 INFO [stderr] Compiling google-content2_sandbox-cli v1.0.7+20171207 (/source) Nov 18 12:02:59.402 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 7.78s Nov 18 12:02:59.423 INFO [stderr] su: No module specific data is present Nov 18 12:03:00.481 INFO running `"docker" "inspect" "41d34bb48bc5b359b53a4a42a197479fb37c71c0589ce4b8b3582c1d01d92917"` Nov 18 12:03:00.833 INFO running `"docker" "rm" "-f" "41d34bb48bc5b359b53a4a42a197479fb37c71c0589ce4b8b3582c1d01d92917"` Nov 18 12:03:01.143 INFO [stdout] 41d34bb48bc5b359b53a4a42a197479fb37c71c0589ce4b8b3582c1d01d92917 Nov 18 12:03:01.153 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 12:03:01.557 INFO [stdout] cb7109a5bd6521154f7d9ffe03df097cb96b23f3e4c92cf71738bffb5a60f16a Nov 18 12:03:01.559 INFO running `"docker" "start" "-a" "cb7109a5bd6521154f7d9ffe03df097cb96b23f3e4c92cf71738bffb5a60f16a"` Nov 18 12:03:02.954 INFO [stderr] usermod: no changes Nov 18 12:03:03.007 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 12:03:03.007 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 12:03:03.007 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 12:03:03.007 INFO [stderr] files will be included as a binary target: Nov 18 12:03:03.007 INFO [stderr] Nov 18 12:03:03.007 INFO [stderr] * /source/src/main.rs Nov 18 12:03:03.007 INFO [stderr] Nov 18 12:03:03.007 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 12:03:03.007 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 12:03:03.007 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 12:03:03.007 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 12:03:03.007 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 12:03:03.007 INFO [stderr] Nov 18 12:03:03.007 INFO [stderr] For more information on this warning you can consult Nov 18 12:03:03.007 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 12:03:03.007 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `content2-sandbox`, Nov 18 12:03:03.007 INFO [stderr] please set bin.path in Cargo.toml Nov 18 12:03:03.175 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.19s Nov 18 12:03:03.190 INFO [stderr] Running /target/debug/deps/content2_sandbox-6c5dd3c6d656ef19 Nov 18 12:03:03.194 INFO [stdout] Nov 18 12:03:03.195 INFO [stdout] running 0 tests Nov 18 12:03:03.195 INFO [stdout] Nov 18 12:03:03.195 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 12:03:03.195 INFO [stdout] Nov 18 12:03:03.202 INFO [stderr] su: No module specific data is present Nov 18 12:03:03.891 INFO running `"docker" "inspect" "cb7109a5bd6521154f7d9ffe03df097cb96b23f3e4c92cf71738bffb5a60f16a"` Nov 18 12:03:04.115 INFO running `"docker" "rm" "-f" "cb7109a5bd6521154f7d9ffe03df097cb96b23f3e4c92cf71738bffb5a60f16a"` Nov 18 12:03:04.329 INFO [stdout] cb7109a5bd6521154f7d9ffe03df097cb96b23f3e4c92cf71738bffb5a60f16a