Nov 18 10:32:33.926 INFO testing google-vault1-cli-1.0.7+20171026 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 10:32:33.928 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:32:34.400 INFO [stdout] a0058367a25d57517dfba2fc2e728947d9cb34f88dc77b735b661036325ed82c
Nov 18 10:32:34.407 INFO running `"docker" "start" "-a" "a0058367a25d57517dfba2fc2e728947d9cb34f88dc77b735b661036325ed82c"`
Nov 18 10:32:36.302 INFO [stderr] usermod: no changes
Nov 18 10:32:36.363 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:32:36.363 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:32:36.363 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:32:36.363 INFO [stderr] files will be included as a binary target:
Nov 18 10:32:36.363 INFO [stderr] 
Nov 18 10:32:36.363 INFO [stderr] * /source/src/main.rs
Nov 18 10:32:36.363 INFO [stderr] 
Nov 18 10:32:36.363 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:32:36.363 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:32:36.363 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:32:36.363 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:32:36.363 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:32:36.363 INFO [stderr] 
Nov 18 10:32:36.363 INFO [stderr] For more information on this warning you can consult
Nov 18 10:32:36.363 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:32:36.363 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `vault1`,
Nov 18 10:32:36.363 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:32:36.542 INFO [stderr]    Compiling google-vault1 v1.0.8+20180827
Nov 18 10:32:45.477 INFO [stderr]    Compiling google-vault1-cli v1.0.7+20171026 (/source)
Nov 18 10:33:02.311 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 25.98s
Nov 18 10:33:02.325 INFO [stderr] su: No module specific data is present
Nov 18 10:33:03.432 INFO running `"docker" "inspect" "a0058367a25d57517dfba2fc2e728947d9cb34f88dc77b735b661036325ed82c"`
Nov 18 10:33:03.689 INFO running `"docker" "rm" "-f" "a0058367a25d57517dfba2fc2e728947d9cb34f88dc77b735b661036325ed82c"`
Nov 18 10:33:04.070 INFO [stdout] a0058367a25d57517dfba2fc2e728947d9cb34f88dc77b735b661036325ed82c
Nov 18 10:33:04.081 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:33:04.527 INFO [stdout] 4e0e7ecdf2fdb98ac127bcd3d07c55c1a9e5d1bae4e10ff17af90d86c564767e
Nov 18 10:33:04.535 INFO running `"docker" "start" "-a" "4e0e7ecdf2fdb98ac127bcd3d07c55c1a9e5d1bae4e10ff17af90d86c564767e"`
Nov 18 10:33:06.650 INFO [stderr] usermod: no changes
Nov 18 10:33:06.711 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:33:06.711 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:33:06.711 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:33:06.711 INFO [stderr] files will be included as a binary target:
Nov 18 10:33:06.711 INFO [stderr] 
Nov 18 10:33:06.711 INFO [stderr] * /source/src/main.rs
Nov 18 10:33:06.711 INFO [stderr] 
Nov 18 10:33:06.711 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:33:06.711 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:33:06.711 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:33:06.711 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:33:06.711 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:33:06.711 INFO [stderr] 
Nov 18 10:33:06.711 INFO [stderr] For more information on this warning you can consult
Nov 18 10:33:06.711 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:33:06.711 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `vault1`,
Nov 18 10:33:06.711 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:33:06.914 INFO [stderr]    Compiling google-vault1-cli v1.0.7+20171026 (/source)
Nov 18 10:33:11.642 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 4.96s
Nov 18 10:33:11.655 INFO [stderr] su: No module specific data is present
Nov 18 10:33:12.274 INFO running `"docker" "inspect" "4e0e7ecdf2fdb98ac127bcd3d07c55c1a9e5d1bae4e10ff17af90d86c564767e"`
Nov 18 10:33:12.581 INFO running `"docker" "rm" "-f" "4e0e7ecdf2fdb98ac127bcd3d07c55c1a9e5d1bae4e10ff17af90d86c564767e"`
Nov 18 10:33:12.862 INFO [stdout] 4e0e7ecdf2fdb98ac127bcd3d07c55c1a9e5d1bae4e10ff17af90d86c564767e
Nov 18 10:33:12.875 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:33:13.373 INFO [stdout] 4fae3b2ec1bd74d18a3fa55a05fbdc418e03f52cd7fe6eaf13a7e20e09519f68
Nov 18 10:33:13.377 INFO running `"docker" "start" "-a" "4fae3b2ec1bd74d18a3fa55a05fbdc418e03f52cd7fe6eaf13a7e20e09519f68"`
Nov 18 10:33:15.309 INFO [stderr] usermod: no changes
Nov 18 10:33:15.403 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 18 10:33:15.403 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 18 10:33:15.403 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 10:33:15.403 INFO [stderr] files will be included as a binary target:
Nov 18 10:33:15.403 INFO [stderr] 
Nov 18 10:33:15.403 INFO [stderr] * /source/src/main.rs
Nov 18 10:33:15.403 INFO [stderr] 
Nov 18 10:33:15.403 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 10:33:15.403 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 18 10:33:15.403 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 18 10:33:15.403 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 10:33:15.403 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 10:33:15.403 INFO [stderr] 
Nov 18 10:33:15.403 INFO [stderr] For more information on this warning you can consult
Nov 18 10:33:15.403 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 10:33:15.403 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `vault1`,
Nov 18 10:33:15.403 INFO [stderr] please set bin.path in Cargo.toml
Nov 18 10:33:15.701 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.36s
Nov 18 10:33:15.707 INFO [stderr]      Running /target/debug/deps/vault1-419648871a85c2d8
Nov 18 10:33:15.712 INFO [stdout] 
Nov 18 10:33:15.712 INFO [stdout] running 0 tests
Nov 18 10:33:15.712 INFO [stdout] 
Nov 18 10:33:15.713 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 10:33:15.713 INFO [stdout] 
Nov 18 10:33:15.719 INFO [stderr] su: No module specific data is present
Nov 18 10:33:17.023 INFO running `"docker" "inspect" "4fae3b2ec1bd74d18a3fa55a05fbdc418e03f52cd7fe6eaf13a7e20e09519f68"`
Nov 18 10:33:17.319 INFO running `"docker" "rm" "-f" "4fae3b2ec1bd74d18a3fa55a05fbdc418e03f52cd7fe6eaf13a7e20e09519f68"`
Nov 18 10:33:17.715 INFO [stdout] 4fae3b2ec1bd74d18a3fa55a05fbdc418e03f52cd7fe6eaf13a7e20e09519f68