Nov 17 17:59:51.996 INFO testing wurl-0.1.0 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 17 17:59:51.997 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 17:59:52.427 INFO [stdout] 2b71e0fc1f7a0eb33f065b1a0e95c0e9876585125800b64317e53976183333eb Nov 17 17:59:52.431 INFO running `"docker" "start" "-a" "2b71e0fc1f7a0eb33f065b1a0e95c0e9876585125800b64317e53976183333eb"` Nov 17 17:59:53.907 INFO [stderr] usermod: no changes Nov 17 17:59:53.943 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 17:59:53.943 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 17:59:53.943 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 17:59:53.943 INFO [stderr] files will be included as a binary target: Nov 17 17:59:53.943 INFO [stderr] Nov 17 17:59:53.943 INFO [stderr] * /source/src/bin/app.rs Nov 17 17:59:53.943 INFO [stderr] * /source/src/bin/messages.rs Nov 17 17:59:53.943 INFO [stderr] Nov 17 17:59:53.943 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 17:59:53.943 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 17:59:53.943 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 17:59:53.943 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 17:59:53.943 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 17:59:53.943 INFO [stderr] Nov 17 17:59:53.943 INFO [stderr] For more information on this warning you can consult Nov 17 17:59:53.943 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 17:59:54.111 INFO [stderr] Compiling mio-extras v2.0.5 Nov 17 17:59:54.112 INFO [stderr] Compiling stderrlog v0.3.0 Nov 17 17:59:57.163 INFO [stderr] Compiling ws v0.7.9 Nov 17 18:00:01.772 INFO [stderr] Compiling wurl v0.1.0 (/source) Nov 17 18:00:13.319 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 19.40s Nov 17 18:00:13.335 INFO [stderr] su: No module specific data is present Nov 17 18:00:14.065 INFO running `"docker" "inspect" "2b71e0fc1f7a0eb33f065b1a0e95c0e9876585125800b64317e53976183333eb"` Nov 17 18:00:14.462 INFO running `"docker" "rm" "-f" "2b71e0fc1f7a0eb33f065b1a0e95c0e9876585125800b64317e53976183333eb"` Nov 17 18:00:14.779 INFO [stdout] 2b71e0fc1f7a0eb33f065b1a0e95c0e9876585125800b64317e53976183333eb Nov 17 18:00:14.783 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 18:00:15.371 INFO [stdout] f601ea39b3ff1cbc7640f90a89e068d8fd33910eece64a50eedfb2fad9dc8342 Nov 17 18:00:15.377 INFO running `"docker" "start" "-a" "f601ea39b3ff1cbc7640f90a89e068d8fd33910eece64a50eedfb2fad9dc8342"` Nov 17 18:00:16.491 INFO [stderr] usermod: no changes Nov 17 18:00:16.579 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 18:00:16.579 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 18:00:16.579 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 18:00:16.579 INFO [stderr] files will be included as a binary target: Nov 17 18:00:16.579 INFO [stderr] Nov 17 18:00:16.579 INFO [stderr] * /source/src/bin/app.rs Nov 17 18:00:16.579 INFO [stderr] * /source/src/bin/messages.rs Nov 17 18:00:16.579 INFO [stderr] Nov 17 18:00:16.579 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 18:00:16.579 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 18:00:16.579 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 18:00:16.579 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 18:00:16.579 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 18:00:16.579 INFO [stderr] Nov 17 18:00:16.579 INFO [stderr] For more information on this warning you can consult Nov 17 18:00:16.579 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 18:00:16.692 INFO [stderr] Compiling wurl v0.1.0 (/source) Nov 17 18:00:21.483 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.95s Nov 17 18:00:21.492 INFO [stderr] su: No module specific data is present Nov 17 18:00:22.016 INFO running `"docker" "inspect" "f601ea39b3ff1cbc7640f90a89e068d8fd33910eece64a50eedfb2fad9dc8342"` Nov 17 18:00:22.299 INFO running `"docker" "rm" "-f" "f601ea39b3ff1cbc7640f90a89e068d8fd33910eece64a50eedfb2fad9dc8342"` Nov 17 18:00:22.663 INFO [stdout] f601ea39b3ff1cbc7640f90a89e068d8fd33910eece64a50eedfb2fad9dc8342 Nov 17 18:00:22.675 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 18:00:23.260 INFO [stdout] eba2a8a7a2284d810573d859733e702fa83de6bf37a08357348958693b7b4845 Nov 17 18:00:23.263 INFO running `"docker" "start" "-a" "eba2a8a7a2284d810573d859733e702fa83de6bf37a08357348958693b7b4845"` Nov 17 18:00:24.627 INFO [stderr] usermod: no changes Nov 17 18:00:24.671 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 18:00:24.671 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 18:00:24.671 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 18:00:24.671 INFO [stderr] files will be included as a binary target: Nov 17 18:00:24.671 INFO [stderr] Nov 17 18:00:24.671 INFO [stderr] * /source/src/bin/app.rs Nov 17 18:00:24.671 INFO [stderr] * /source/src/bin/messages.rs Nov 17 18:00:24.671 INFO [stderr] Nov 17 18:00:24.671 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 18:00:24.671 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 18:00:24.671 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 18:00:24.671 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 18:00:24.671 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 18:00:24.671 INFO [stderr] Nov 17 18:00:24.671 INFO [stderr] For more information on this warning you can consult Nov 17 18:00:24.671 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 18:00:24.763 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.11s Nov 17 18:00:24.779 INFO [stderr] Running /target/debug/deps/wurl-0e8128ad64d04b63 Nov 17 18:00:24.780 INFO [stdout] Nov 17 18:00:24.780 INFO [stdout] running 0 tests Nov 17 18:00:24.780 INFO [stdout] Nov 17 18:00:24.780 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 18:00:24.780 INFO [stdout] Nov 17 18:00:24.783 INFO [stderr] Running /target/debug/deps/wurl-6e9a99d079d0aaf3 Nov 17 18:00:24.790 INFO [stdout] Nov 17 18:00:24.790 INFO [stdout] running 1 test Nov 17 18:00:24.790 INFO [stdout] test messages::tests::test_parse_message ... ok Nov 17 18:00:24.790 INFO [stdout] Nov 17 18:00:24.790 INFO [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 18:00:24.790 INFO [stdout] Nov 17 18:00:24.795 INFO [stderr] Doc-tests wurl Nov 17 18:00:27.446 INFO [stdout] Nov 17 18:00:27.446 INFO [stdout] running 0 tests Nov 17 18:00:27.446 INFO [stdout] Nov 17 18:00:27.446 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 18:00:27.446 INFO [stdout] Nov 17 18:00:27.455 INFO [stderr] su: No module specific data is present Nov 17 18:00:28.583 INFO running `"docker" "inspect" "eba2a8a7a2284d810573d859733e702fa83de6bf37a08357348958693b7b4845"` Nov 17 18:00:29.045 INFO running `"docker" "rm" "-f" "eba2a8a7a2284d810573d859733e702fa83de6bf37a08357348958693b7b4845"` Nov 17 18:00:29.435 INFO [stdout] eba2a8a7a2284d810573d859733e702fa83de6bf37a08357348958693b7b4845