Nov 17 14:28:28.676 INFO testing JoonHoSon/rust_hello against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 17 14:28:28.676 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 17 14:28:29.211 INFO [stdout] e0399d5db0ccb63005da1cf81250fab463fcf5e9e6ecb14e674f9d7f49768579
Nov 17 14:28:29.215 INFO running `"docker" "start" "-a" "e0399d5db0ccb63005da1cf81250fab463fcf5e9e6ecb14e674f9d7f49768579"`
Nov 17 14:28:30.251 INFO [stderr] usermod: no changes
Nov 17 14:28:30.303 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 14:28:30.303 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 14:28:30.303 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 14:28:30.303 INFO [stderr] files will be included as a binary target:
Nov 17 14:28:30.303 INFO [stderr] 
Nov 17 14:28:30.303 INFO [stderr] * /source/src/main.rs
Nov 17 14:28:30.303 INFO [stderr] 
Nov 17 14:28:30.303 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 14:28:30.303 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 14:28:30.303 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 14:28:30.303 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 14:28:30.303 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 14:28:30.303 INFO [stderr] 
Nov 17 14:28:30.303 INFO [stderr] For more information on this warning you can consult
Nov 17 14:28:30.303 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 14:28:30.303 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `hello-joonho`,
Nov 17 14:28:30.303 INFO [stderr] please set bin.path in Cargo.toml
Nov 17 14:28:30.315 INFO [stderr]    Compiling hello v0.1.0 (/source)
Nov 17 14:28:31.184 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.90s
Nov 17 14:28:31.186 INFO [stderr] su: No module specific data is present
Nov 17 14:28:32.343 INFO running `"docker" "inspect" "e0399d5db0ccb63005da1cf81250fab463fcf5e9e6ecb14e674f9d7f49768579"`
Nov 17 14:28:32.632 INFO running `"docker" "rm" "-f" "e0399d5db0ccb63005da1cf81250fab463fcf5e9e6ecb14e674f9d7f49768579"`
Nov 17 14:28:32.959 INFO [stdout] e0399d5db0ccb63005da1cf81250fab463fcf5e9e6ecb14e674f9d7f49768579
Nov 17 14:28:32.964 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 17 14:28:33.532 INFO [stdout] 93ea8d299d97043b46134b89b54d5106e611de4cce9534e19e908cfdb552f030
Nov 17 14:28:33.540 INFO running `"docker" "start" "-a" "93ea8d299d97043b46134b89b54d5106e611de4cce9534e19e908cfdb552f030"`
Nov 17 14:28:34.323 INFO [stderr] usermod: no changes
Nov 17 14:28:34.359 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 14:28:34.361 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 14:28:34.361 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 14:28:34.361 INFO [stderr] files will be included as a binary target:
Nov 17 14:28:34.361 INFO [stderr] 
Nov 17 14:28:34.361 INFO [stderr] * /source/src/main.rs
Nov 17 14:28:34.361 INFO [stderr] 
Nov 17 14:28:34.361 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 14:28:34.361 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 14:28:34.361 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 14:28:34.361 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 14:28:34.361 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 14:28:34.361 INFO [stderr] 
Nov 17 14:28:34.361 INFO [stderr] For more information on this warning you can consult
Nov 17 14:28:34.362 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 14:28:34.362 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `hello-joonho`,
Nov 17 14:28:34.362 INFO [stderr] please set bin.path in Cargo.toml
Nov 17 14:28:34.362 INFO [stderr]    Compiling hello v0.1.0 (/source)
Nov 17 14:28:35.174 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.82s
Nov 17 14:28:35.174 INFO [stderr] su: No module specific data is present
Nov 17 14:28:35.605 INFO running `"docker" "inspect" "93ea8d299d97043b46134b89b54d5106e611de4cce9534e19e908cfdb552f030"`
Nov 17 14:28:35.881 INFO running `"docker" "rm" "-f" "93ea8d299d97043b46134b89b54d5106e611de4cce9534e19e908cfdb552f030"`
Nov 17 14:28:36.175 INFO [stdout] 93ea8d299d97043b46134b89b54d5106e611de4cce9534e19e908cfdb552f030
Nov 17 14:28:36.184 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/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 17 14:28:36.633 INFO [stdout] d5e1d9d4749b67d22c1bd08814ae1d9bad92a908f2fa10ec2757d02ce17a960e
Nov 17 14:28:36.634 INFO running `"docker" "start" "-a" "d5e1d9d4749b67d22c1bd08814ae1d9bad92a908f2fa10ec2757d02ce17a960e"`
Nov 17 14:28:37.823 INFO [stderr] usermod: no changes
Nov 17 14:28:37.907 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 14:28:37.907 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 14:28:37.907 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 14:28:37.907 INFO [stderr] files will be included as a binary target:
Nov 17 14:28:37.907 INFO [stderr] 
Nov 17 14:28:37.907 INFO [stderr] * /source/src/main.rs
Nov 17 14:28:37.907 INFO [stderr] 
Nov 17 14:28:37.907 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 14:28:37.907 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 14:28:37.907 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 14:28:37.907 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 14:28:37.907 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 14:28:37.907 INFO [stderr] 
Nov 17 14:28:37.907 INFO [stderr] For more information on this warning you can consult
Nov 17 14:28:37.907 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 14:28:37.907 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `hello-joonho`,
Nov 17 14:28:37.907 INFO [stderr] please set bin.path in Cargo.toml
Nov 17 14:28:37.907 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.04s
Nov 17 14:28:37.914 INFO [stderr]      Running /target/debug/deps/hello_joonho-193ad7f248073ee2
Nov 17 14:28:37.921 INFO [stdout] 
Nov 17 14:28:37.921 INFO [stdout] running 0 tests
Nov 17 14:28:37.921 INFO [stdout] 
Nov 17 14:28:37.921 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 14:28:37.921 INFO [stdout] 
Nov 17 14:28:37.922 INFO [stderr] su: No module specific data is present
Nov 17 14:28:38.548 INFO running `"docker" "inspect" "d5e1d9d4749b67d22c1bd08814ae1d9bad92a908f2fa10ec2757d02ce17a960e"`
Nov 17 14:28:38.775 INFO running `"docker" "rm" "-f" "d5e1d9d4749b67d22c1bd08814ae1d9bad92a908f2fa10ec2757d02ce17a960e"`
Nov 17 14:28:39.033 INFO [stdout] d5e1d9d4749b67d22c1bd08814ae1d9bad92a908f2fa10ec2757d02ce17a960e