Nov 17 10:50:21.610 INFO testing WanzenBug/lzw-rs against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982 Nov 17 10:50:21.610 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:50:22.079 INFO [stdout] 387e6c546f5db5722d56d37a8cc96f3828604442e60279bd65dc02ac483191d6 Nov 17 10:50:22.081 INFO running `"docker" "start" "-a" "387e6c546f5db5722d56d37a8cc96f3828604442e60279bd65dc02ac483191d6"` Nov 17 10:50:23.574 INFO [stderr] usermod: no changes Nov 17 10:50:23.640 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 10:50:23.640 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 10:50:23.640 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 10:50:23.640 INFO [stderr] files will be included as a binary target: Nov 17 10:50:23.640 INFO [stderr] Nov 17 10:50:23.640 INFO [stderr] * /source/src/bin/util.rs Nov 17 10:50:23.640 INFO [stderr] Nov 17 10:50:23.640 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 10:50:23.640 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 10:50:23.640 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 10:50:23.640 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 10:50:23.640 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 10:50:23.640 INFO [stderr] Nov 17 10:50:23.640 INFO [stderr] For more information on this warning you can consult Nov 17 10:50:23.640 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 10:50:23.687 INFO [stderr] Compiling bitstream-rs v0.1.2 Nov 17 10:50:24.139 INFO [stderr] Compiling lzw-rs v0.1.0 (/source) Nov 17 10:50:25.799 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.20s Nov 17 10:50:25.804 INFO [stderr] su: No module specific data is present Nov 17 10:50:26.505 INFO running `"docker" "inspect" "387e6c546f5db5722d56d37a8cc96f3828604442e60279bd65dc02ac483191d6"` Nov 17 10:50:26.843 INFO running `"docker" "rm" "-f" "387e6c546f5db5722d56d37a8cc96f3828604442e60279bd65dc02ac483191d6"` Nov 17 10:50:27.156 INFO [stdout] 387e6c546f5db5722d56d37a8cc96f3828604442e60279bd65dc02ac483191d6 Nov 17 10:50:27.165 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:50:27.583 INFO [stdout] 4c1e9d15c02cc27c1cdd23e7027d3a87a7b2ac2b600e94757a2ffe96882041c2 Nov 17 10:50:27.585 INFO running `"docker" "start" "-a" "4c1e9d15c02cc27c1cdd23e7027d3a87a7b2ac2b600e94757a2ffe96882041c2"` Nov 17 10:50:28.691 INFO [stderr] usermod: no changes Nov 17 10:50:28.734 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 10:50:28.734 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 10:50:28.734 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 10:50:28.734 INFO [stderr] files will be included as a binary target: Nov 17 10:50:28.734 INFO [stderr] Nov 17 10:50:28.734 INFO [stderr] * /source/src/bin/util.rs Nov 17 10:50:28.734 INFO [stderr] Nov 17 10:50:28.734 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 10:50:28.734 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 10:50:28.734 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 10:50:28.734 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 10:50:28.734 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 10:50:28.734 INFO [stderr] Nov 17 10:50:28.734 INFO [stderr] For more information on this warning you can consult Nov 17 10:50:28.734 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 10:50:28.766 INFO [stderr] Compiling lzw-rs v0.1.0 (/source) Nov 17 10:50:30.043 INFO [stderr] warning: unnecessary parentheses around function argument Nov 17 10:50:30.043 INFO [stderr] --> src/util.rs:136:36 Nov 17 10:50:30.044 INFO [stderr] | Nov 17 10:50:30.044 INFO [stderr] 136 | assert_eq!(it.next(), Some((1))); Nov 17 10:50:30.044 INFO [stderr] | ^^^ help: remove these parentheses Nov 17 10:50:30.044 INFO [stderr] | Nov 17 10:50:30.045 INFO [stderr] = note: #[warn(unused_parens)] on by default Nov 17 10:50:30.045 INFO [stderr] Nov 17 10:50:30.045 INFO [stderr] warning: unnecessary parentheses around function argument Nov 17 10:50:30.045 INFO [stderr] --> src/util.rs:137:36 Nov 17 10:50:30.046 INFO [stderr] | Nov 17 10:50:30.046 INFO [stderr] 137 | assert_eq!(it.next(), Some((2))); Nov 17 10:50:30.046 INFO [stderr] | ^^^ help: remove these parentheses Nov 17 10:50:30.046 INFO [stderr] Nov 17 10:50:30.047 INFO [stderr] warning: unnecessary parentheses around function argument Nov 17 10:50:30.047 INFO [stderr] --> src/util.rs:138:36 Nov 17 10:50:30.047 INFO [stderr] | Nov 17 10:50:30.047 INFO [stderr] 138 | assert_eq!(it.next(), Some((2))); Nov 17 10:50:30.048 INFO [stderr] | ^^^ help: remove these parentheses Nov 17 10:50:30.048 INFO [stderr] Nov 17 10:50:30.048 INFO [stderr] warning: unnecessary parentheses around function argument Nov 17 10:50:30.048 INFO [stderr] --> src/util.rs:139:36 Nov 17 10:50:30.049 INFO [stderr] | Nov 17 10:50:30.049 INFO [stderr] 139 | assert_eq!(it.next(), Some((3))); Nov 17 10:50:30.049 INFO [stderr] | ^^^ help: remove these parentheses Nov 17 10:50:30.049 INFO [stderr] Nov 17 10:50:31.242 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.52s Nov 17 10:50:31.246 INFO [stderr] su: No module specific data is present Nov 17 10:50:31.777 INFO running `"docker" "inspect" "4c1e9d15c02cc27c1cdd23e7027d3a87a7b2ac2b600e94757a2ffe96882041c2"` Nov 17 10:50:32.043 INFO running `"docker" "rm" "-f" "4c1e9d15c02cc27c1cdd23e7027d3a87a7b2ac2b600e94757a2ffe96882041c2"` Nov 17 10:50:32.313 INFO [stdout] 4c1e9d15c02cc27c1cdd23e7027d3a87a7b2ac2b600e94757a2ffe96882041c2 Nov 17 10:50:32.319 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-2/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 10:50:32.923 INFO [stdout] 63b3dc50981845af99e8b332ae204f9b66d110110cbfdb08640c0a6c86720a35 Nov 17 10:50:32.927 INFO running `"docker" "start" "-a" "63b3dc50981845af99e8b332ae204f9b66d110110cbfdb08640c0a6c86720a35"` Nov 17 10:50:33.857 INFO [stderr] usermod: no changes Nov 17 10:50:33.891 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Nov 17 10:50:33.891 INFO [stderr] disables Cargo from automatically inferring other binary targets. Nov 17 10:50:33.891 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Nov 17 10:50:33.891 INFO [stderr] files will be included as a binary target: Nov 17 10:50:33.891 INFO [stderr] Nov 17 10:50:33.891 INFO [stderr] * /source/src/bin/util.rs Nov 17 10:50:33.891 INFO [stderr] Nov 17 10:50:33.891 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Nov 17 10:50:33.891 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Nov 17 10:50:33.891 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Nov 17 10:50:33.891 INFO [stderr] section. You may also move the files to a location where Cargo would not Nov 17 10:50:33.891 INFO [stderr] automatically infer them to be a target, such as in subfolders. Nov 17 10:50:33.891 INFO [stderr] Nov 17 10:50:33.891 INFO [stderr] For more information on this warning you can consult Nov 17 10:50:33.891 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Nov 17 10:50:33.914 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.03s Nov 17 10:50:33.915 INFO [stderr] Running /target/debug/deps/lzw-8d9571baffb7477c Nov 17 10:50:33.927 INFO [stdout] Nov 17 10:50:33.927 INFO [stdout] running 3 tests Nov 17 10:50:33.927 INFO [stdout] test util::tests::test_enumerator ... ok Nov 17 10:50:33.927 INFO [stdout] test tests::test_lzw_writer ... ok Nov 17 10:50:33.928 INFO [stdout] test util::tests::test_bit_index ... ok Nov 17 10:50:33.928 INFO [stderr] Running /target/debug/deps/decode-34279f850ead6655 Nov 17 10:50:33.928 INFO [stdout] Nov 17 10:50:33.928 INFO [stdout] test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 10:50:33.928 INFO [stdout] Nov 17 10:50:33.939 INFO [stdout] Nov 17 10:50:33.939 INFO [stdout] running 0 tests Nov 17 10:50:33.939 INFO [stdout] Nov 17 10:50:33.939 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 10:50:33.939 INFO [stdout] Nov 17 10:50:33.939 INFO [stdout] Nov 17 10:50:33.939 INFO [stdout] running 0 tests Nov 17 10:50:33.939 INFO [stdout] Nov 17 10:50:33.939 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 10:50:33.939 INFO [stdout] Nov 17 10:50:33.939 INFO [stderr] Running /target/debug/deps/encode-c18bb7d92feda69d Nov 17 10:50:33.939 INFO [stderr] Doc-tests lzw Nov 17 10:50:34.447 INFO [stdout] Nov 17 10:50:34.447 INFO [stdout] running 0 tests Nov 17 10:50:34.448 INFO [stdout] Nov 17 10:50:34.448 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Nov 17 10:50:34.448 INFO [stdout] Nov 17 10:50:34.457 INFO [stderr] su: No module specific data is present Nov 17 10:50:35.207 INFO running `"docker" "inspect" "63b3dc50981845af99e8b332ae204f9b66d110110cbfdb08640c0a6c86720a35"` Nov 17 10:50:35.567 INFO running `"docker" "rm" "-f" "63b3dc50981845af99e8b332ae204f9b66d110110cbfdb08640c0a6c86720a35"` Nov 17 10:50:35.825 INFO [stdout] 63b3dc50981845af99e8b332ae204f9b66d110110cbfdb08640c0a6c86720a35