Nov 18 10:40:52.306 INFO testing google-storagetransfer1-cli-1.0.7+20171202 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 18 10:40:52.307 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:40:52.747 INFO [stdout] 3d0433fa712332bb1d396dc93138eaafad8801ddb2505100b51fbc16cb6e7fcf Nov 18 10:40:52.750 INFO running `"docker" "start" "-a" "3d0433fa712332bb1d396dc93138eaafad8801ddb2505100b51fbc16cb6e7fcf"` Nov 18 10:40:55.326 INFO [stderr] usermod: no changes Nov 18 10:40:55.403 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:40:55.403 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:40:55.403 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:40:55.403 INFO [stderr] files will be included as a binary target: Nov 18 10:40:55.403 INFO [stderr] Nov 18 10:40:55.403 INFO [stderr] * /source/src/main.rs Nov 18 10:40:55.403 INFO [stderr] Nov 18 10:40:55.403 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:40:55.403 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:40:55.403 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:40:55.403 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:40:55.403 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:40:55.403 INFO [stderr] Nov 18 10:40:55.403 INFO [stderr] For more information on this warning you can consult Nov 18 10:40:55.403 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:40:55.403 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `storagetransfer1`, Nov 18 10:40:55.403 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:40:55.753 INFO [stderr] Compiling ring v0.13.5 Nov 18 10:40:55.755 INFO [stderr] Compiling yup-hyper-mock v2.0.0 Nov 18 10:40:55.756 INFO [stderr] Compiling hyper-native-tls v0.3.0 Nov 18 10:41:03.039 INFO [stderr] Compiling yup-oauth2 v1.0.9 Nov 18 10:41:12.403 INFO [stderr] Compiling sct v0.4.0 Nov 18 10:41:12.451 INFO [stderr] Compiling webpki v0.18.1 Nov 18 10:41:14.259 INFO [stderr] Compiling google-storagetransfer1 v1.0.8+20181008 Nov 18 10:41:16.733 INFO [stderr] Compiling rustls v0.13.1 Nov 18 10:41:16.741 INFO [stderr] Compiling webpki-roots v0.15.0 Nov 18 10:41:38.105 INFO [stderr] Compiling hyper-rustls v0.6.2 Nov 18 10:41:40.810 INFO [stderr] Compiling google-storagetransfer1-cli v1.0.7+20171202 (/source) Nov 18 10:42:01.974 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1m 06s Nov 18 10:42:01.991 INFO [stderr] su: No module specific data is present Nov 18 10:42:03.309 INFO running `"docker" "inspect" "3d0433fa712332bb1d396dc93138eaafad8801ddb2505100b51fbc16cb6e7fcf"` Nov 18 10:42:03.687 INFO running `"docker" "rm" "-f" "3d0433fa712332bb1d396dc93138eaafad8801ddb2505100b51fbc16cb6e7fcf"` Nov 18 10:42:04.023 INFO [stdout] 3d0433fa712332bb1d396dc93138eaafad8801ddb2505100b51fbc16cb6e7fcf Nov 18 10:42:04.032 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:42:04.516 INFO [stdout] d6f1b79e12e55f6e1941c7d08d2440cdcf45034526528dfb3fa7077be432cf8f Nov 18 10:42:04.518 INFO running `"docker" "start" "-a" "d6f1b79e12e55f6e1941c7d08d2440cdcf45034526528dfb3fa7077be432cf8f"` Nov 18 10:42:06.806 INFO [stderr] usermod: no changes Nov 18 10:42:06.871 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:42:06.871 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:42:06.871 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:42:06.871 INFO [stderr] files will be included as a binary target: Nov 18 10:42:06.871 INFO [stderr] Nov 18 10:42:06.871 INFO [stderr] * /source/src/main.rs Nov 18 10:42:06.871 INFO [stderr] Nov 18 10:42:06.871 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:42:06.871 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:42:06.871 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:42:06.871 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:42:06.871 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:42:06.871 INFO [stderr] Nov 18 10:42:06.871 INFO [stderr] For more information on this warning you can consult Nov 18 10:42:06.871 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:42:06.871 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `storagetransfer1`, Nov 18 10:42:06.871 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:42:07.082 INFO [stderr] Compiling google-storagetransfer1-cli v1.0.7+20171202 (/source) Nov 18 10:42:12.532 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 5.70s Nov 18 10:42:12.549 INFO [stderr] su: No module specific data is present Nov 18 10:42:13.627 INFO running `"docker" "inspect" "d6f1b79e12e55f6e1941c7d08d2440cdcf45034526528dfb3fa7077be432cf8f"` Nov 18 10:42:14.033 INFO running `"docker" "rm" "-f" "d6f1b79e12e55f6e1941c7d08d2440cdcf45034526528dfb3fa7077be432cf8f"` Nov 18 10:42:14.327 INFO [stdout] d6f1b79e12e55f6e1941c7d08d2440cdcf45034526528dfb3fa7077be432cf8f Nov 18 10:42:14.334 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-7/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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:42:14.775 INFO [stdout] 97cb0464ab2dcf5d20c898d75c1044ee0b49bd6f53a2bb7b5d34e2d36e599c84 Nov 18 10:42:14.778 INFO running `"docker" "start" "-a" "97cb0464ab2dcf5d20c898d75c1044ee0b49bd6f53a2bb7b5d34e2d36e599c84"` Nov 18 10:42:17.171 INFO [stderr] usermod: no changes Nov 18 10:42:17.227 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:42:17.227 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:42:17.227 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:42:17.227 INFO [stderr] files will be included as a binary target: Nov 18 10:42:17.227 INFO [stderr] Nov 18 10:42:17.227 INFO [stderr] * /source/src/main.rs Nov 18 10:42:17.227 INFO [stderr] Nov 18 10:42:17.227 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:42:17.227 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:42:17.227 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:42:17.227 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:42:17.227 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:42:17.227 INFO [stderr] Nov 18 10:42:17.227 INFO [stderr] For more information on this warning you can consult Nov 18 10:42:17.227 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:42:17.227 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `storagetransfer1`, Nov 18 10:42:17.227 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:42:17.376 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.18s Nov 18 10:42:17.393 INFO [stderr] Running /target/debug/deps/storagetransfer1-725dacc6a5d8c44f Nov 18 10:42:17.403 INFO [stdout] Nov 18 10:42:17.403 INFO [stdout] running 0 tests Nov 18 10:42:17.403 INFO [stdout] Nov 18 10:42:17.403 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 10:42:17.403 INFO [stdout] Nov 18 10:42:17.406 INFO [stderr] su: No module specific data is present Nov 18 10:42:18.811 INFO running `"docker" "inspect" "97cb0464ab2dcf5d20c898d75c1044ee0b49bd6f53a2bb7b5d34e2d36e599c84"` Nov 18 10:42:19.167 INFO running `"docker" "rm" "-f" "97cb0464ab2dcf5d20c898d75c1044ee0b49bd6f53a2bb7b5d34e2d36e599c84"` Nov 18 10:42:19.530 INFO [stdout] 97cb0464ab2dcf5d20c898d75c1044ee0b49bd6f53a2bb7b5d34e2d36e599c84