Nov 16 17:02:50.003 INFO testing pgrzesik/rust-web-server against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 16 17:02:50.003 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 16 17:02:50.710 INFO [stdout] 8ab7322181d849e695dbe6f5590e0433003bd77a56edb80f358590e90a424208 Nov 16 17:02:50.713 INFO running `"docker" "start" "-a" "8ab7322181d849e695dbe6f5590e0433003bd77a56edb80f358590e90a424208"` Nov 16 17:02:51.963 INFO [stderr] usermod: no changes Nov 16 17:02:52.021 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 16 17:02:52.022 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 16 17:02:52.022 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 16 17:02:52.022 INFO [stderr] files will be included as a binary target: Nov 16 17:02:52.023 INFO [stderr] Nov 16 17:02:52.023 INFO [stderr] * /source/src/main.rs Nov 16 17:02:52.023 INFO [stderr] Nov 16 17:02:52.024 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 16 17:02:52.024 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 16 17:02:52.024 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 16 17:02:52.025 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 16 17:02:52.025 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 16 17:02:52.025 INFO [stderr] Nov 16 17:02:52.026 INFO [stderr] For more information on this warning you can consult Nov 16 17:02:52.026 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 16 17:02:52.026 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Nov 16 17:02:52.026 INFO [stderr] please set bin.path in Cargo.toml Nov 16 17:02:52.027 INFO [stderr] Compiling rust_web_server v0.1.0 (/source) Nov 16 17:02:54.418 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.43s Nov 16 17:02:54.421 INFO [stderr] su: No module specific data is present Nov 16 17:02:55.143 INFO running `"docker" "inspect" "8ab7322181d849e695dbe6f5590e0433003bd77a56edb80f358590e90a424208"` Nov 16 17:02:55.521 INFO running `"docker" "rm" "-f" "8ab7322181d849e695dbe6f5590e0433003bd77a56edb80f358590e90a424208"` Nov 16 17:02:55.810 INFO [stdout] 8ab7322181d849e695dbe6f5590e0433003bd77a56edb80f358590e90a424208 Nov 16 17:02:55.817 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 16 17:02:56.171 INFO [stdout] e03d3c9fb0acbb962ebad9060366796db32425817e7f6a09716f7ee4e8d21d05 Nov 16 17:02:56.173 INFO running `"docker" "start" "-a" "e03d3c9fb0acbb962ebad9060366796db32425817e7f6a09716f7ee4e8d21d05"` Nov 16 17:02:58.166 INFO [stderr] usermod: no changes Nov 16 17:02:58.235 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 16 17:02:58.236 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 16 17:02:58.236 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 16 17:02:58.236 INFO [stderr] files will be included as a binary target: Nov 16 17:02:58.236 INFO [stderr] Nov 16 17:02:58.237 INFO [stderr] * /source/src/main.rs Nov 16 17:02:58.237 INFO [stderr] Nov 16 17:02:58.237 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 16 17:02:58.238 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 16 17:02:58.238 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 16 17:02:58.238 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 16 17:02:58.239 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 16 17:02:58.239 INFO [stderr] Nov 16 17:02:58.239 INFO [stderr] For more information on this warning you can consult Nov 16 17:02:58.240 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 16 17:02:58.240 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Nov 16 17:02:58.240 INFO [stderr] please set bin.path in Cargo.toml Nov 16 17:02:58.243 INFO [stderr] Compiling rust_web_server v0.1.0 (/source) Nov 16 17:02:59.299 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.10s Nov 16 17:02:59.302 INFO [stderr] su: No module specific data is present Nov 16 17:03:00.383 INFO running `"docker" "inspect" "e03d3c9fb0acbb962ebad9060366796db32425817e7f6a09716f7ee4e8d21d05"` Nov 16 17:03:00.646 INFO running `"docker" "rm" "-f" "e03d3c9fb0acbb962ebad9060366796db32425817e7f6a09716f7ee4e8d21d05"` Nov 16 17:03:01.013 INFO [stdout] e03d3c9fb0acbb962ebad9060366796db32425817e7f6a09716f7ee4e8d21d05 Nov 16 17:03:01.014 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-0/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 16 17:03:01.548 INFO [stdout] 634f2e5f2eddedbfff36f6beb498ceb622e6402a6dbf3e9630506dc7665b0b64 Nov 16 17:03:01.556 INFO running `"docker" "start" "-a" "634f2e5f2eddedbfff36f6beb498ceb622e6402a6dbf3e9630506dc7665b0b64"` Nov 16 17:03:02.771 INFO [stderr] usermod: no changes Nov 16 17:03:02.831 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 16 17:03:02.831 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 16 17:03:02.831 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 16 17:03:02.831 INFO [stderr] files will be included as a binary target: Nov 16 17:03:02.831 INFO [stderr] Nov 16 17:03:02.831 INFO [stderr] * /source/src/main.rs Nov 16 17:03:02.831 INFO [stderr] Nov 16 17:03:02.831 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 16 17:03:02.831 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 16 17:03:02.831 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 16 17:03:02.831 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 16 17:03:02.831 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 16 17:03:02.831 INFO [stderr] Nov 16 17:03:02.831 INFO [stderr] For more information on this warning you can consult Nov 16 17:03:02.831 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 16 17:03:02.831 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `rust-web-server`, Nov 16 17:03:02.831 INFO [stderr] please set bin.path in Cargo.toml Nov 16 17:03:02.834 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.02s Nov 16 17:03:02.835 INFO [stderr] Running /target/debug/deps/rust_web_server-ce922a54680cf682 Nov 16 17:03:02.851 INFO [stderr] Running /target/debug/deps/rust_web_server-4b42a7b9a939f15a Nov 16 17:03:02.851 INFO [stderr] Doc-tests rust_web_server Nov 16 17:03:02.852 INFO [stdout] Nov 16 17:03:02.852 INFO [stdout] running 0 tests Nov 16 17:03:02.852 INFO [stdout] Nov 16 17:03:02.852 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 16 17:03:02.852 INFO [stdout] Nov 16 17:03:02.852 INFO [stdout] Nov 16 17:03:02.852 INFO [stdout] running 0 tests Nov 16 17:03:02.852 INFO [stdout] Nov 16 17:03:02.852 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 16 17:03:02.852 INFO [stdout] Nov 16 17:03:03.164 INFO [stdout] Nov 16 17:03:03.164 INFO [stdout] running 0 tests Nov 16 17:03:03.164 INFO [stdout] Nov 16 17:03:03.164 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 16 17:03:03.164 INFO [stdout] Nov 16 17:03:03.168 INFO [stderr] su: No module specific data is present Nov 16 17:03:03.789 INFO running `"docker" "inspect" "634f2e5f2eddedbfff36f6beb498ceb622e6402a6dbf3e9630506dc7665b0b64"` Nov 16 17:03:04.109 INFO running `"docker" "rm" "-f" "634f2e5f2eddedbfff36f6beb498ceb622e6402a6dbf3e9630506dc7665b0b64"` Nov 16 17:03:04.567 INFO [stdout] 634f2e5f2eddedbfff36f6beb498ceb622e6402a6dbf3e9630506dc7665b0b64