Nov 18 11:57:26.091 INFO testing google-datastore1_beta3-cli-1.0.7+20171205 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 18 11:57:26.091 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 11:57:26.421 INFO [stdout] 3474d6eb3b4ec10cf76fdfa383342ab0c02b9f17519635057b5dd0b1e6c38669 Nov 18 11:57:26.423 INFO running `"docker" "start" "-a" "3474d6eb3b4ec10cf76fdfa383342ab0c02b9f17519635057b5dd0b1e6c38669"` Nov 18 11:57:28.614 INFO [stderr] usermod: no changes Nov 18 11:57:28.651 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 11:57:28.651 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 11:57:28.651 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 11:57:28.651 INFO [stderr] files will be included as a binary target: Nov 18 11:57:28.651 INFO [stderr] Nov 18 11:57:28.651 INFO [stderr] * /source/src/main.rs Nov 18 11:57:28.651 INFO [stderr] Nov 18 11:57:28.651 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 11:57:28.651 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 11:57:28.651 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 11:57:28.651 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 11:57:28.651 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 11:57:28.651 INFO [stderr] Nov 18 11:57:28.651 INFO [stderr] For more information on this warning you can consult Nov 18 11:57:28.651 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 11:57:28.651 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `datastore1-beta3`, Nov 18 11:57:28.651 INFO [stderr] please set bin.path in Cargo.toml Nov 18 11:57:28.841 INFO [stderr] Compiling google-datastore1_beta3 v1.0.8+20181002 Nov 18 11:57:36.779 INFO [stderr] Compiling google-datastore1_beta3-cli v1.0.7+20171205 (/source) Nov 18 11:57:56.362 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 27.72s Nov 18 11:57:56.375 INFO [stderr] su: No module specific data is present Nov 18 11:57:57.628 INFO running `"docker" "inspect" "3474d6eb3b4ec10cf76fdfa383342ab0c02b9f17519635057b5dd0b1e6c38669"` Nov 18 11:57:57.937 INFO running `"docker" "rm" "-f" "3474d6eb3b4ec10cf76fdfa383342ab0c02b9f17519635057b5dd0b1e6c38669"` Nov 18 11:57:58.294 INFO [stdout] 3474d6eb3b4ec10cf76fdfa383342ab0c02b9f17519635057b5dd0b1e6c38669 Nov 18 11:57:58.297 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 11:57:58.755 INFO [stdout] 7e2aeccf33ae90ce72b93a38872f5612ac1df3872fef18f2571d8cdec31a5c6f Nov 18 11:57:58.759 INFO running `"docker" "start" "-a" "7e2aeccf33ae90ce72b93a38872f5612ac1df3872fef18f2571d8cdec31a5c6f"` Nov 18 11:58:00.135 INFO [stderr] usermod: no changes Nov 18 11:58:00.175 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 11:58:00.175 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 11:58:00.175 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 11:58:00.175 INFO [stderr] files will be included as a binary target: Nov 18 11:58:00.175 INFO [stderr] Nov 18 11:58:00.175 INFO [stderr] * /source/src/main.rs Nov 18 11:58:00.175 INFO [stderr] Nov 18 11:58:00.175 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 11:58:00.175 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 11:58:00.175 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 11:58:00.175 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 11:58:00.175 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 11:58:00.175 INFO [stderr] Nov 18 11:58:00.175 INFO [stderr] For more information on this warning you can consult Nov 18 11:58:00.175 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 11:58:00.175 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `datastore1-beta3`, Nov 18 11:58:00.175 INFO [stderr] please set bin.path in Cargo.toml Nov 18 11:58:00.359 INFO [stderr] Compiling google-datastore1_beta3-cli v1.0.7+20171205 (/source) Nov 18 11:58:06.393 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 6.23s Nov 18 11:58:06.412 INFO [stderr] su: No module specific data is present Nov 18 11:58:07.900 INFO running `"docker" "inspect" "7e2aeccf33ae90ce72b93a38872f5612ac1df3872fef18f2571d8cdec31a5c6f"` Nov 18 11:58:08.291 INFO running `"docker" "rm" "-f" "7e2aeccf33ae90ce72b93a38872f5612ac1df3872fef18f2571d8cdec31a5c6f"` Nov 18 11:58:08.670 INFO [stdout] 7e2aeccf33ae90ce72b93a38872f5612ac1df3872fef18f2571d8cdec31a5c6f Nov 18 11:58:08.676 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 11:58:09.175 INFO [stdout] 98cb7933ac0cc0c4af9bad46e0dd312e2444116df0c76918d289690deb813d85 Nov 18 11:58:09.176 INFO running `"docker" "start" "-a" "98cb7933ac0cc0c4af9bad46e0dd312e2444116df0c76918d289690deb813d85"` Nov 18 11:58:11.382 INFO [stderr] usermod: no changes Nov 18 11:58:11.486 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 11:58:11.486 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 11:58:11.486 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 11:58:11.486 INFO [stderr] files will be included as a binary target: Nov 18 11:58:11.486 INFO [stderr] Nov 18 11:58:11.486 INFO [stderr] * /source/src/main.rs Nov 18 11:58:11.486 INFO [stderr] Nov 18 11:58:11.486 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 11:58:11.486 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 11:58:11.486 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 11:58:11.486 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 11:58:11.486 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 11:58:11.486 INFO [stderr] Nov 18 11:58:11.486 INFO [stderr] For more information on this warning you can consult Nov 18 11:58:11.486 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 11:58:11.486 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `datastore1-beta3`, Nov 18 11:58:11.486 INFO [stderr] please set bin.path in Cargo.toml Nov 18 11:58:11.717 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.30s Nov 18 11:58:11.725 INFO [stderr] Running /target/debug/deps/datastore1_beta3-1099062f879327eb Nov 18 11:58:11.737 INFO [stdout] Nov 18 11:58:11.737 INFO [stdout] running 0 tests Nov 18 11:58:11.737 INFO [stdout] Nov 18 11:58:11.737 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 11:58:11.737 INFO [stdout] Nov 18 11:58:11.742 INFO [stderr] su: No module specific data is present Nov 18 11:58:12.727 INFO running `"docker" "inspect" "98cb7933ac0cc0c4af9bad46e0dd312e2444116df0c76918d289690deb813d85"` Nov 18 11:58:13.096 INFO running `"docker" "rm" "-f" "98cb7933ac0cc0c4af9bad46e0dd312e2444116df0c76918d289690deb813d85"` Nov 18 11:58:13.435 INFO [stdout] 98cb7933ac0cc0c4af9bad46e0dd312e2444116df0c76918d289690deb813d85