Nov 18 12:00:22.822 INFO testing google-dataproc1-cli-1.0.7+20171207 against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 18 12:00:22.823 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 12:00:23.291 INFO [stdout] 3139ff111a34a851b41d74908a52ac71e206057519001313b31b0baeb60d9d27
Nov 18 12:00:23.294 INFO running `"docker" "start" "-a" "3139ff111a34a851b41d74908a52ac71e206057519001313b31b0baeb60d9d27"`
Nov 18 12:00:25.627 INFO [stderr] usermod: no changes
Nov 18 12:00:25.699 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:00:25.699 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:00:25.699 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:00:25.699 INFO [stderr] files will be included as a binary target:
Nov 18 12:00:25.699 INFO [stderr] 
Nov 18 12:00:25.699 INFO [stderr] * /source/src/main.rs
Nov 18 12:00:25.699 INFO [stderr] 
Nov 18 12:00:25.699 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:00:25.699 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:00:25.699 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:00:25.699 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:00:25.699 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:00:25.699 INFO [stderr] 
Nov 18 12:00:25.699 INFO [stderr] For more information on this warning you can consult
Nov 18 12:00:25.699 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:00:25.699 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dataproc1`,
Nov 18 12:00:25.699 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:00:25.935 INFO [stderr]    Compiling google-dataproc1 v1.0.8+20181005
Nov 18 12:00:37.815 INFO [stderr]    Compiling google-dataproc1-cli v1.0.7+20171207 (/source)
Nov 18 12:01:00.007 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 34.35s
Nov 18 12:01:00.015 INFO [stderr] su: No module specific data is present
Nov 18 12:01:01.050 INFO running `"docker" "inspect" "3139ff111a34a851b41d74908a52ac71e206057519001313b31b0baeb60d9d27"`
Nov 18 12:01:01.311 INFO running `"docker" "rm" "-f" "3139ff111a34a851b41d74908a52ac71e206057519001313b31b0baeb60d9d27"`
Nov 18 12:01:01.595 INFO [stdout] 3139ff111a34a851b41d74908a52ac71e206057519001313b31b0baeb60d9d27
Nov 18 12:01:01.600 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 12:01:02.016 INFO [stdout] 7992085922b750b5af1fff84a750f8426257289c062abeba494d4e77dc5bcfb0
Nov 18 12:01:02.023 INFO running `"docker" "start" "-a" "7992085922b750b5af1fff84a750f8426257289c062abeba494d4e77dc5bcfb0"`
Nov 18 12:01:03.482 INFO [stderr] usermod: no changes
Nov 18 12:01:03.531 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:01:03.531 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:01:03.531 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:01:03.531 INFO [stderr] files will be included as a binary target:
Nov 18 12:01:03.531 INFO [stderr] 
Nov 18 12:01:03.531 INFO [stderr] * /source/src/main.rs
Nov 18 12:01:03.531 INFO [stderr] 
Nov 18 12:01:03.531 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:01:03.531 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:01:03.531 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:01:03.531 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:01:03.531 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:01:03.531 INFO [stderr] 
Nov 18 12:01:03.531 INFO [stderr] For more information on this warning you can consult
Nov 18 12:01:03.531 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:01:03.531 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dataproc1`,
Nov 18 12:01:03.531 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:01:03.686 INFO [stderr]    Compiling google-dataproc1-cli v1.0.7+20171207 (/source)
Nov 18 12:01:10.080 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.58s
Nov 18 12:01:10.095 INFO [stderr] su: No module specific data is present
Nov 18 12:01:11.019 INFO running `"docker" "inspect" "7992085922b750b5af1fff84a750f8426257289c062abeba494d4e77dc5bcfb0"`
Nov 18 12:01:11.383 INFO running `"docker" "rm" "-f" "7992085922b750b5af1fff84a750f8426257289c062abeba494d4e77dc5bcfb0"`
Nov 18 12:01:11.718 INFO [stdout] 7992085922b750b5af1fff84a750f8426257289c062abeba494d4e77dc5bcfb0
Nov 18 12:01:11.727 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-6/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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 12:01:12.167 INFO [stdout] b254fc1301dffd49b474aa8cfc4688c45fc1db4e60da92acf725822cca445f8f
Nov 18 12:01:12.175 INFO running `"docker" "start" "-a" "b254fc1301dffd49b474aa8cfc4688c45fc1db4e60da92acf725822cca445f8f"`
Nov 18 12:01:13.610 INFO [stderr] usermod: no changes
Nov 18 12:01:13.688 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 12:01:13.688 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 12:01:13.688 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 12:01:13.688 INFO [stderr] files will be included as a binary target:
Nov 18 12:01:13.688 INFO [stderr] 
Nov 18 12:01:13.688 INFO [stderr] * /source/src/main.rs
Nov 18 12:01:13.688 INFO [stderr] 
Nov 18 12:01:13.688 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 12:01:13.688 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 12:01:13.688 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 12:01:13.690 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 12:01:13.690 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 12:01:13.690 INFO [stderr] 
Nov 18 12:01:13.690 INFO [stderr] For more information on this warning you can consult
Nov 18 12:01:13.690 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 12:01:13.690 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `dataproc1`,
Nov 18 12:01:13.690 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 12:01:13.852 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.20s
Nov 18 12:01:13.871 INFO [stderr]      Running /target/debug/deps/dataproc1-5f37d8c895506cb1
Nov 18 12:01:13.875 INFO [stderr] su: No module specific data is present
Nov 18 12:01:13.876 INFO [stdout] 
Nov 18 12:01:13.876 INFO [stdout] running 0 tests
Nov 18 12:01:13.876 INFO [stdout] 
Nov 18 12:01:13.876 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 12:01:13.877 INFO [stdout] 
Nov 18 12:01:14.579 INFO running `"docker" "inspect" "b254fc1301dffd49b474aa8cfc4688c45fc1db4e60da92acf725822cca445f8f"`
Nov 18 12:01:14.899 INFO running `"docker" "rm" "-f" "b254fc1301dffd49b474aa8cfc4688c45fc1db4e60da92acf725822cca445f8f"`
Nov 18 12:01:15.099 INFO [stdout] b254fc1301dffd49b474aa8cfc4688c45fc1db4e60da92acf725822cca445f8f