Dec 05 11:33:09.306 INFO testing pgrzesik/rust-web-server against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514 Dec 05 11:33:09.306 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-1/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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 05 11:33:09.768 INFO [stdout] f0359862d2243820cb5750f0fe2b70d4907b76cfc044af60e64731c4d6d86082 Dec 05 11:33:09.776 INFO running `"docker" "start" "-a" "f0359862d2243820cb5750f0fe2b70d4907b76cfc044af60e64731c4d6d86082"` Dec 05 11:33:11.044 INFO [stderr] usermod: no changes Dec 05 11:33:11.104 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 05 11:33:11.104 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 05 11:33:11.104 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 05 11:33:11.104 INFO [stderr] files will be included as a binary target: Dec 05 11:33:11.104 INFO [stderr] Dec 05 11:33:11.104 INFO [stderr] * /source/src/main.rs Dec 05 11:33:11.104 INFO [stderr] Dec 05 11:33:11.104 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 05 11:33:11.104 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 05 11:33:11.104 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 05 11:33:11.104 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 05 11:33:11.104 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 05 11:33:11.104 INFO [stderr] Dec 05 11:33:11.104 INFO [stderr] For more information on this warning you can consult Dec 05 11:33:11.104 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 05 11:33:11.104 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Dec 05 11:33:11.104 INFO [stderr] please set bin.path in Cargo.toml Dec 05 11:33:11.124 INFO [stderr] Compiling rust_web_server v0.1.0 (/source) Dec 05 11:33:13.492 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.42s Dec 05 11:33:13.492 INFO [stderr] su: No module specific data is present Dec 05 11:33:14.246 INFO running `"docker" "inspect" "f0359862d2243820cb5750f0fe2b70d4907b76cfc044af60e64731c4d6d86082"` Dec 05 11:33:14.674 INFO running `"docker" "rm" "-f" "f0359862d2243820cb5750f0fe2b70d4907b76cfc044af60e64731c4d6d86082"` Dec 05 11:33:14.909 INFO [stdout] f0359862d2243820cb5750f0fe2b70d4907b76cfc044af60e64731c4d6d86082 Dec 05 11:33:14.918 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-1/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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 05 11:33:15.328 INFO [stdout] c1cf54870ba19164d72a463ff1b495f74ab8ccfa0da1a5538e1eaaf7a090ee30 Dec 05 11:33:15.332 INFO running `"docker" "start" "-a" "c1cf54870ba19164d72a463ff1b495f74ab8ccfa0da1a5538e1eaaf7a090ee30"` Dec 05 11:33:16.386 INFO [stderr] usermod: no changes Dec 05 11:33:16.430 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 05 11:33:16.430 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 05 11:33:16.430 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 05 11:33:16.430 INFO [stderr] files will be included as a binary target: Dec 05 11:33:16.430 INFO [stderr] Dec 05 11:33:16.430 INFO [stderr] * /source/src/main.rs Dec 05 11:33:16.430 INFO [stderr] Dec 05 11:33:16.430 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 05 11:33:16.430 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 05 11:33:16.430 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 05 11:33:16.430 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 05 11:33:16.430 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 05 11:33:16.430 INFO [stderr] Dec 05 11:33:16.430 INFO [stderr] For more information on this warning you can consult Dec 05 11:33:16.430 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 05 11:33:16.430 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Dec 05 11:33:16.430 INFO [stderr] please set bin.path in Cargo.toml Dec 05 11:33:16.432 INFO [stderr] Compiling rust_web_server v0.1.0 (/source) Dec 05 11:33:17.527 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.11s Dec 05 11:33:17.544 INFO [stderr] su: No module specific data is present Dec 05 11:33:18.421 INFO running `"docker" "inspect" "c1cf54870ba19164d72a463ff1b495f74ab8ccfa0da1a5538e1eaaf7a090ee30"` Dec 05 11:33:18.678 INFO running `"docker" "rm" "-f" "c1cf54870ba19164d72a463ff1b495f74ab8ccfa0da1a5538e1eaaf7a090ee30"` Dec 05 11:33:18.968 INFO [stdout] c1cf54870ba19164d72a463ff1b495f74ab8ccfa0da1a5538e1eaaf7a090ee30 Dec 05 11:33:18.973 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-1/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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 05 11:33:19.420 INFO [stdout] e382d67bbcf0d112a1b343620a92b9a6787305c4e0aaaaf88953e8c5f48525ba Dec 05 11:33:19.440 INFO running `"docker" "start" "-a" "e382d67bbcf0d112a1b343620a92b9a6787305c4e0aaaaf88953e8c5f48525ba"` Dec 05 11:33:20.610 INFO [stderr] usermod: no changes Dec 05 11:33:20.645 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 05 11:33:20.645 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 05 11:33:20.645 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 05 11:33:20.645 INFO [stderr] files will be included as a binary target: Dec 05 11:33:20.645 INFO [stderr] Dec 05 11:33:20.645 INFO [stderr] * /source/src/main.rs Dec 05 11:33:20.645 INFO [stderr] Dec 05 11:33:20.645 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 05 11:33:20.645 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 05 11:33:20.645 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 05 11:33:20.645 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 05 11:33:20.646 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 05 11:33:20.646 INFO [stderr] Dec 05 11:33:20.646 INFO [stderr] For more information on this warning you can consult Dec 05 11:33:20.646 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 05 11:33:20.646 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Dec 05 11:33:20.646 INFO [stderr] please set bin.path in Cargo.toml Dec 05 11:33:20.646 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.01s Dec 05 11:33:20.646 INFO [stderr] Running /target/debug/deps/rust_web_server-89b5d62037e082be Dec 05 11:33:20.654 INFO [stdout] Dec 05 11:33:20.654 INFO [stdout] running 0 tests Dec 05 11:33:20.654 INFO [stdout] Dec 05 11:33:20.654 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 05 11:33:20.654 INFO [stdout] Dec 05 11:33:20.656 INFO [stdout] Dec 05 11:33:20.656 INFO [stderr] Running /target/debug/deps/rust_web_server-4e9cf0bfc3ba64aa Dec 05 11:33:20.656 INFO [stdout] running 0 tests Dec 05 11:33:20.656 INFO [stderr] Doc-tests rust_web_server Dec 05 11:33:20.656 INFO [stdout] Dec 05 11:33:20.656 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 05 11:33:20.656 INFO [stdout] Dec 05 11:33:21.023 INFO [stdout] Dec 05 11:33:21.023 INFO [stdout] running 0 tests Dec 05 11:33:21.023 INFO [stdout] Dec 05 11:33:21.023 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 05 11:33:21.023 INFO [stdout] Dec 05 11:33:21.032 INFO [stderr] su: No module specific data is present Dec 05 11:33:21.660 INFO running `"docker" "inspect" "e382d67bbcf0d112a1b343620a92b9a6787305c4e0aaaaf88953e8c5f48525ba"` Dec 05 11:33:21.987 INFO running `"docker" "rm" "-f" "e382d67bbcf0d112a1b343620a92b9a6787305c4e0aaaaf88953e8c5f48525ba"` Dec 05 11:33:22.298 INFO [stdout] e382d67bbcf0d112a1b343620a92b9a6787305c4e0aaaaf88953e8c5f48525ba