Nov 18 10:50:44.974 INFO testing google-runtimeconfig1-cli-1.0.7+20171030 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 18 10:50:44.976 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/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:50:45.239 INFO [stdout] cdf85b506117f0e2c62c89829b348d39949f1633e11b14eefb936ee351249d9b Nov 18 10:50:45.241 INFO running `"docker" "start" "-a" "cdf85b506117f0e2c62c89829b348d39949f1633e11b14eefb936ee351249d9b"` Nov 18 10:50:45.749 INFO [stderr] usermod: no changes Nov 18 10:50:45.786 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:50:45.787 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:50:45.787 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:50:45.787 INFO [stderr] files will be included as a binary target: Nov 18 10:50:45.787 INFO [stderr] Nov 18 10:50:45.787 INFO [stderr] * /source/src/main.rs Nov 18 10:50:45.787 INFO [stderr] Nov 18 10:50:45.787 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:50:45.787 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:50:45.787 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:50:45.787 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:50:45.787 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:50:45.787 INFO [stderr] Nov 18 10:50:45.787 INFO [stderr] For more information on this warning you can consult Nov 18 10:50:45.787 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:50:45.787 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `runtimeconfig1`, Nov 18 10:50:45.787 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:50:45.911 INFO [stderr] Compiling google-runtimeconfig1 v1.0.8+20180924 Nov 18 10:50:50.601 INFO [stderr] Compiling google-runtimeconfig1-cli v1.0.7+20171030 (/source) Nov 18 10:51:04.195 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 18.42s Nov 18 10:51:04.211 INFO [stderr] su: No module specific data is present Nov 18 10:51:04.696 INFO running `"docker" "inspect" "cdf85b506117f0e2c62c89829b348d39949f1633e11b14eefb936ee351249d9b"` Nov 18 10:51:04.811 INFO running `"docker" "rm" "-f" "cdf85b506117f0e2c62c89829b348d39949f1633e11b14eefb936ee351249d9b"` Nov 18 10:51:04.930 INFO [stdout] cdf85b506117f0e2c62c89829b348d39949f1633e11b14eefb936ee351249d9b Nov 18 10:51:04.933 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/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:51:05.225 INFO [stdout] 88cb0ae5e42cee78b12569e466ad066c94e808746a735e415826712d06bb2d5b Nov 18 10:51:05.227 INFO running `"docker" "start" "-a" "88cb0ae5e42cee78b12569e466ad066c94e808746a735e415826712d06bb2d5b"` Nov 18 10:51:05.832 INFO [stderr] usermod: no changes Nov 18 10:51:05.864 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:51:05.864 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:51:05.864 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:51:05.864 INFO [stderr] files will be included as a binary target: Nov 18 10:51:05.864 INFO [stderr] Nov 18 10:51:05.864 INFO [stderr] * /source/src/main.rs Nov 18 10:51:05.865 INFO [stderr] Nov 18 10:51:05.865 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:51:05.865 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:51:05.865 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:51:05.865 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:51:05.865 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:51:05.865 INFO [stderr] Nov 18 10:51:05.865 INFO [stderr] For more information on this warning you can consult Nov 18 10:51:05.865 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:51:05.865 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `runtimeconfig1`, Nov 18 10:51:05.865 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:51:05.999 INFO [stderr] Compiling google-runtimeconfig1-cli v1.0.7+20171030 (/source) Nov 18 10:51:10.480 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.63s Nov 18 10:51:10.493 INFO [stderr] su: No module specific data is present Nov 18 10:51:10.784 INFO running `"docker" "inspect" "88cb0ae5e42cee78b12569e466ad066c94e808746a735e415826712d06bb2d5b"` Nov 18 10:51:10.860 INFO running `"docker" "rm" "-f" "88cb0ae5e42cee78b12569e466ad066c94e808746a735e415826712d06bb2d5b"` Nov 18 10:51:10.942 INFO [stdout] 88cb0ae5e42cee78b12569e466ad066c94e808746a735e415826712d06bb2d5b Nov 18 10:51:10.944 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-3/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/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:51:11.155 INFO [stdout] f8bf70aeeb50807f08d7a358c0756127ddcca07e7345922966bd8a93d617b031 Nov 18 10:51:11.158 INFO running `"docker" "start" "-a" "f8bf70aeeb50807f08d7a358c0756127ddcca07e7345922966bd8a93d617b031"` Nov 18 10:51:11.689 INFO [stderr] usermod: no changes Nov 18 10:51:11.719 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 18 10:51:11.720 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 18 10:51:11.720 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 18 10:51:11.720 INFO [stderr] files will be included as a binary target: Nov 18 10:51:11.720 INFO [stderr] Nov 18 10:51:11.721 INFO [stderr] * /source/src/main.rs Nov 18 10:51:11.721 INFO [stderr] Nov 18 10:51:11.721 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 18 10:51:11.721 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 18 10:51:11.722 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 18 10:51:11.722 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 18 10:51:11.722 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 18 10:51:11.723 INFO [stderr] Nov 18 10:51:11.723 INFO [stderr] For more information on this warning you can consult Nov 18 10:51:11.723 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 18 10:51:11.723 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `runtimeconfig1`, Nov 18 10:51:11.724 INFO [stderr] please set bin.path in Cargo.toml Nov 18 10:51:11.846 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.14s Nov 18 10:51:11.863 INFO [stderr] Running /target/debug/deps/runtimeconfig1-d0975a66ae9d7e8b Nov 18 10:51:11.870 INFO [stdout] Nov 18 10:51:11.870 INFO [stdout] running 0 tests Nov 18 10:51:11.870 INFO [stdout] Nov 18 10:51:11.870 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 18 10:51:11.870 INFO [stdout] Nov 18 10:51:11.871 INFO [stderr] su: No module specific data is present Nov 18 10:51:12.191 INFO running `"docker" "inspect" "f8bf70aeeb50807f08d7a358c0756127ddcca07e7345922966bd8a93d617b031"` Nov 18 10:51:12.307 INFO running `"docker" "rm" "-f" "f8bf70aeeb50807f08d7a358c0756127ddcca07e7345922966bd8a93d617b031"` Nov 18 10:51:12.415 INFO [stdout] f8bf70aeeb50807f08d7a358c0756127ddcca07e7345922966bd8a93d617b031