Dec 13 07:36:08.959 INFO testing pgrzesik/rust-web-server against try#aa49d8ef14939ddec0e34b346b60174a5673d48f for pr-56550 Dec 13 07:36:08.959 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-4/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 13 07:36:09.531 INFO [stdout] e0427d2356b4f06d8f8328ac49c0c74edefcfd693902bf3f76b0c669a7ac9622 Dec 13 07:36:09.533 INFO running `"docker" "start" "-a" "e0427d2356b4f06d8f8328ac49c0c74edefcfd693902bf3f76b0c669a7ac9622"` Dec 13 07:36:10.663 INFO [stderr] usermod: no changes Dec 13 07:36:10.715 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 13 07:36:10.715 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 13 07:36:10.715 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 13 07:36:10.715 INFO [stderr] files will be included as a binary target: Dec 13 07:36:10.715 INFO [stderr] Dec 13 07:36:10.715 INFO [stderr] * /source/src/main.rs Dec 13 07:36:10.715 INFO [stderr] Dec 13 07:36:10.715 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 13 07:36:10.715 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 13 07:36:10.715 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 13 07:36:10.715 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 13 07:36:10.715 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 13 07:36:10.715 INFO [stderr] Dec 13 07:36:10.715 INFO [stderr] For more information on this warning you can consult Dec 13 07:36:10.715 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 13 07:36:10.715 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Dec 13 07:36:10.715 INFO [stderr] please set bin.path in Cargo.toml Dec 13 07:36:10.715 INFO [stderr] Compiling rust_web_server v0.1.0 (/source) Dec 13 07:36:13.091 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.40s Dec 13 07:36:13.094 INFO [stderr] su: No module specific data is present Dec 13 07:36:13.893 INFO running `"docker" "inspect" "e0427d2356b4f06d8f8328ac49c0c74edefcfd693902bf3f76b0c669a7ac9622"` Dec 13 07:36:14.198 INFO running `"docker" "rm" "-f" "e0427d2356b4f06d8f8328ac49c0c74edefcfd693902bf3f76b0c669a7ac9622"` Dec 13 07:36:14.574 INFO [stdout] e0427d2356b4f06d8f8328ac49c0c74edefcfd693902bf3f76b0c669a7ac9622 Dec 13 07:36:14.578 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-4/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 13 07:36:14.984 INFO [stdout] 64c501fb8aa2567cbdebe40e742da225255d531fe5dc002bce2eb7a461d994b9 Dec 13 07:36:14.988 INFO running `"docker" "start" "-a" "64c501fb8aa2567cbdebe40e742da225255d531fe5dc002bce2eb7a461d994b9"` Dec 13 07:36:16.235 INFO [stderr] usermod: no changes Dec 13 07:36:16.319 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 13 07:36:16.319 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 13 07:36:16.319 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 13 07:36:16.319 INFO [stderr] files will be included as a binary target: Dec 13 07:36:16.319 INFO [stderr] Dec 13 07:36:16.319 INFO [stderr] * /source/src/main.rs Dec 13 07:36:16.319 INFO [stderr] Dec 13 07:36:16.319 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 13 07:36:16.319 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 13 07:36:16.319 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 13 07:36:16.319 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 13 07:36:16.319 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 13 07:36:16.319 INFO [stderr] Dec 13 07:36:16.319 INFO [stderr] For more information on this warning you can consult Dec 13 07:36:16.319 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 13 07:36:16.319 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Dec 13 07:36:16.319 INFO [stderr] please set bin.path in Cargo.toml Dec 13 07:36:16.339 INFO [stderr] Compiling rust_web_server v0.1.0 (/source) Dec 13 07:36:17.467 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.19s Dec 13 07:36:17.469 INFO [stderr] su: No module specific data is present Dec 13 07:36:18.151 INFO running `"docker" "inspect" "64c501fb8aa2567cbdebe40e742da225255d531fe5dc002bce2eb7a461d994b9"` Dec 13 07:36:18.359 INFO running `"docker" "rm" "-f" "64c501fb8aa2567cbdebe40e742da225255d531fe5dc002bce2eb7a461d994b9"` Dec 13 07:36:18.687 INFO [stdout] 64c501fb8aa2567cbdebe40e742da225255d531fe5dc002bce2eb7a461d994b9 Dec 13 07:36:18.693 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56550/worker-4/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-56550/try#aa49d8ef14939ddec0e34b346b60174a5673d48f:/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 +aa49d8ef14939ddec0e34b346b60174a5673d48f-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"` Dec 13 07:36:19.089 INFO [stdout] 427aef5e702ba361c062d88c279e79f4231b1ece732aac636d7e0c29c1cc9a80 Dec 13 07:36:19.089 INFO running `"docker" "start" "-a" "427aef5e702ba361c062d88c279e79f4231b1ece732aac636d7e0c29c1cc9a80"` Dec 13 07:36:20.342 INFO [stderr] usermod: no changes Dec 13 07:36:20.387 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 13 07:36:20.387 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 13 07:36:20.387 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 13 07:36:20.387 INFO [stderr] files will be included as a binary target: Dec 13 07:36:20.387 INFO [stderr] Dec 13 07:36:20.387 INFO [stderr] * /source/src/main.rs Dec 13 07:36:20.387 INFO [stderr] Dec 13 07:36:20.387 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 13 07:36:20.387 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 13 07:36:20.387 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 13 07:36:20.387 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 13 07:36:20.387 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 13 07:36:20.387 INFO [stderr] Dec 13 07:36:20.387 INFO [stderr] For more information on this warning you can consult Dec 13 07:36:20.387 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 13 07:36:20.387 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Dec 13 07:36:20.387 INFO [stderr] please set bin.path in Cargo.toml Dec 13 07:36:20.387 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.02s Dec 13 07:36:20.391 INFO [stderr] Running /target/debug/deps/rust_web_server-1e3b82872924e0ab Dec 13 07:36:20.393 INFO [stdout] Dec 13 07:36:20.393 INFO [stdout] running 0 tests Dec 13 07:36:20.393 INFO [stdout] Dec 13 07:36:20.393 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 13 07:36:20.393 INFO [stdout] Dec 13 07:36:20.395 INFO [stderr] Running /target/debug/deps/rust_web_server-2382e6e1ba86d356 Dec 13 07:36:20.395 INFO [stdout] Dec 13 07:36:20.395 INFO [stdout] running 0 tests Dec 13 07:36:20.395 INFO [stdout] Dec 13 07:36:20.395 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 13 07:36:20.395 INFO [stdout] Dec 13 07:36:20.399 INFO [stderr] Doc-tests rust_web_server Dec 13 07:36:20.824 INFO [stdout] Dec 13 07:36:20.824 INFO [stdout] running 0 tests Dec 13 07:36:20.824 INFO [stdout] Dec 13 07:36:20.824 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 13 07:36:20.824 INFO [stdout] Dec 13 07:36:20.835 INFO [stderr] su: No module specific data is present Dec 13 07:36:21.669 INFO running `"docker" "inspect" "427aef5e702ba361c062d88c279e79f4231b1ece732aac636d7e0c29c1cc9a80"` Dec 13 07:36:21.869 INFO running `"docker" "rm" "-f" "427aef5e702ba361c062d88c279e79f4231b1ece732aac636d7e0c29c1cc9a80"` Dec 13 07:36:22.075 INFO [stdout] 427aef5e702ba361c062d88c279e79f4231b1ece732aac636d7e0c29c1cc9a80