Dec 02 02:18:39.621 INFO testing WanzenBug/lzw-rs against 1.30.1 for beta-1.31-5
Dec 02 02:18:39.621 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-7/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/beta-1.31-5/1.30.1:/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 +1.30.1 build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 02:18:40.095 INFO [stdout] f1d302306a3be94eaa9dfc92e8c54253b533d8acb3b5e4650b8c7188004175d3
Dec 02 02:18:40.103 INFO running `"docker" "start" "-a" "f1d302306a3be94eaa9dfc92e8c54253b533d8acb3b5e4650b8c7188004175d3"`
Dec 02 02:18:41.378 INFO [stderr] usermod: no changes
Dec 02 02:18:41.436 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 02 02:18:41.436 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 02 02:18:41.436 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 02:18:41.436 INFO [stderr] files will be included as a binary target:
Dec 02 02:18:41.436 INFO [stderr] 
Dec 02 02:18:41.436 INFO [stderr] * /source/src/bin/util.rs
Dec 02 02:18:41.436 INFO [stderr] 
Dec 02 02:18:41.436 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 02:18:41.436 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 02 02:18:41.436 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 02 02:18:41.436 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 02:18:41.436 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 02:18:41.436 INFO [stderr] 
Dec 02 02:18:41.436 INFO [stderr] For more information on this warning you can consult
Dec 02 02:18:41.436 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 02:18:41.507 INFO [stderr]    Compiling bitstream-rs v0.1.2
Dec 02 02:18:42.079 INFO [stderr]    Compiling lzw-rs v0.1.0 (/source)
Dec 02 02:18:44.823 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.39s
Dec 02 02:18:44.823 INFO [stderr] su: No module specific data is present
Dec 02 02:18:45.716 INFO running `"docker" "inspect" "f1d302306a3be94eaa9dfc92e8c54253b533d8acb3b5e4650b8c7188004175d3"`
Dec 02 02:18:45.996 INFO running `"docker" "rm" "-f" "f1d302306a3be94eaa9dfc92e8c54253b533d8acb3b5e4650b8c7188004175d3"`
Dec 02 02:18:46.267 INFO [stdout] f1d302306a3be94eaa9dfc92e8c54253b533d8acb3b5e4650b8c7188004175d3
Dec 02 02:18:46.269 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-7/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/beta-1.31-5/1.30.1:/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 +1.30.1 test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 02:18:46.751 INFO [stdout] 688aebd073309957b82eaffd187c2258a421c750dd50ae0951391d6b243c6a57
Dec 02 02:18:46.757 INFO running `"docker" "start" "-a" "688aebd073309957b82eaffd187c2258a421c750dd50ae0951391d6b243c6a57"`
Dec 02 02:18:47.982 INFO [stderr] usermod: no changes
Dec 02 02:18:48.039 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 02 02:18:48.039 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 02 02:18:48.039 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 02:18:48.039 INFO [stderr] files will be included as a binary target:
Dec 02 02:18:48.039 INFO [stderr] 
Dec 02 02:18:48.039 INFO [stderr] * /source/src/bin/util.rs
Dec 02 02:18:48.039 INFO [stderr] 
Dec 02 02:18:48.039 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 02:18:48.039 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 02 02:18:48.039 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 02 02:18:48.039 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 02:18:48.039 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 02:18:48.039 INFO [stderr] 
Dec 02 02:18:48.039 INFO [stderr] For more information on this warning you can consult
Dec 02 02:18:48.039 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 02:18:48.053 INFO [stderr]    Compiling lzw-rs v0.1.0 (/source)
Dec 02 02:18:49.135 INFO [stderr] warning: unnecessary parentheses around function argument
Dec 02 02:18:49.135 INFO [stderr]    --> src/util.rs:136:36
Dec 02 02:18:49.135 INFO [stderr]     |
Dec 02 02:18:49.135 INFO [stderr] 136 |         assert_eq!(it.next(), Some((1)));
Dec 02 02:18:49.135 INFO [stderr]     |                                    ^^^ help: remove these parentheses
Dec 02 02:18:49.135 INFO [stderr]     |
Dec 02 02:18:49.135 INFO [stderr]     = note: #[warn(unused_parens)] on by default
Dec 02 02:18:49.135 INFO [stderr] 
Dec 02 02:18:49.136 INFO [stderr] warning: unnecessary parentheses around function argument
Dec 02 02:18:49.136 INFO [stderr]    --> src/util.rs:137:36
Dec 02 02:18:49.136 INFO [stderr]     |
Dec 02 02:18:49.136 INFO [stderr] 137 |         assert_eq!(it.next(), Some((2)));
Dec 02 02:18:49.136 INFO [stderr]     |                                    ^^^ help: remove these parentheses
Dec 02 02:18:49.136 INFO [stderr] 
Dec 02 02:18:49.136 INFO [stderr] warning: unnecessary parentheses around function argument
Dec 02 02:18:49.136 INFO [stderr]    --> src/util.rs:138:36
Dec 02 02:18:49.136 INFO [stderr]     |
Dec 02 02:18:49.136 INFO [stderr] 138 |         assert_eq!(it.next(), Some((2)));
Dec 02 02:18:49.136 INFO [stderr]     |                                    ^^^ help: remove these parentheses
Dec 02 02:18:49.136 INFO [stderr] 
Dec 02 02:18:49.136 INFO [stderr] warning: unnecessary parentheses around function argument
Dec 02 02:18:49.136 INFO [stderr]    --> src/util.rs:139:36
Dec 02 02:18:49.136 INFO [stderr]     |
Dec 02 02:18:49.136 INFO [stderr] 139 |         assert_eq!(it.next(), Some((3)));
Dec 02 02:18:49.136 INFO [stderr]     |                                    ^^^ help: remove these parentheses
Dec 02 02:18:49.136 INFO [stderr] 
Dec 02 02:18:50.477 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.45s
Dec 02 02:18:50.477 INFO [stderr] su: No module specific data is present
Dec 02 02:18:51.143 INFO running `"docker" "inspect" "688aebd073309957b82eaffd187c2258a421c750dd50ae0951391d6b243c6a57"`
Dec 02 02:18:51.471 INFO running `"docker" "rm" "-f" "688aebd073309957b82eaffd187c2258a421c750dd50ae0951391d6b243c6a57"`
Dec 02 02:18:51.761 INFO [stdout] 688aebd073309957b82eaffd187c2258a421c750dd50ae0951391d6b243c6a57
Dec 02 02:18:51.769 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-7/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/beta-1.31-5/1.30.1:/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 +1.30.1 test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 02:18:52.119 INFO [stdout] 4cc0877bdd083b37461d58785c0961d9ac175dbf360b9579fe71dd4a9054d206
Dec 02 02:18:52.125 INFO running `"docker" "start" "-a" "4cc0877bdd083b37461d58785c0961d9ac175dbf360b9579fe71dd4a9054d206"`
Dec 02 02:18:53.554 INFO [stderr] usermod: no changes
Dec 02 02:18:53.614 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 02 02:18:53.614 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 02 02:18:53.614 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 02:18:53.614 INFO [stderr] files will be included as a binary target:
Dec 02 02:18:53.614 INFO [stderr] 
Dec 02 02:18:53.614 INFO [stderr] * /source/src/bin/util.rs
Dec 02 02:18:53.614 INFO [stderr] 
Dec 02 02:18:53.614 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 02:18:53.614 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 02 02:18:53.614 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 02 02:18:53.615 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 02:18:53.615 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 02:18:53.615 INFO [stderr] 
Dec 02 02:18:53.615 INFO [stderr] For more information on this warning you can consult
Dec 02 02:18:53.615 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 02:18:53.643 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.05s
Dec 02 02:18:53.646 INFO [stderr]      Running /target/debug/deps/lzw-7446484d8c0af842
Dec 02 02:18:53.657 INFO [stdout] 
Dec 02 02:18:53.657 INFO [stdout] running 3 tests
Dec 02 02:18:53.657 INFO [stdout] test util::tests::test_bit_index ... ok
Dec 02 02:18:53.657 INFO [stdout] test util::tests::test_enumerator ... ok
Dec 02 02:18:53.667 INFO [stdout] test tests::test_lzw_writer ... ok
Dec 02 02:18:53.667 INFO [stdout] 
Dec 02 02:18:53.667 INFO [stdout] test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 02 02:18:53.667 INFO [stdout] 
Dec 02 02:18:53.667 INFO [stderr]      Running /target/debug/deps/decode-c4bc41d3a400d5b8
Dec 02 02:18:53.669 INFO [stdout] 
Dec 02 02:18:53.669 INFO [stdout] running 0 tests
Dec 02 02:18:53.669 INFO [stdout] 
Dec 02 02:18:53.669 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 02 02:18:53.669 INFO [stdout] 
Dec 02 02:18:53.671 INFO [stderr]      Running /target/debug/deps/encode-60dd2ac747c5938f
Dec 02 02:18:53.672 INFO [stdout] 
Dec 02 02:18:53.674 INFO [stdout] running 0 tests
Dec 02 02:18:53.674 INFO [stdout] 
Dec 02 02:18:53.674 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 02 02:18:53.674 INFO [stdout] 
Dec 02 02:18:53.677 INFO [stderr]    Doc-tests lzw
Dec 02 02:18:54.527 INFO [stdout] 
Dec 02 02:18:54.527 INFO [stdout] running 0 tests
Dec 02 02:18:54.527 INFO [stdout] 
Dec 02 02:18:54.527 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 02 02:18:54.527 INFO [stdout] 
Dec 02 02:18:54.535 INFO [stderr] su: No module specific data is present
Dec 02 02:18:55.095 INFO running `"docker" "inspect" "4cc0877bdd083b37461d58785c0961d9ac175dbf360b9579fe71dd4a9054d206"`
Dec 02 02:18:55.435 INFO running `"docker" "rm" "-f" "4cc0877bdd083b37461d58785c0961d9ac175dbf360b9579fe71dd4a9054d206"`
Dec 02 02:18:55.835 INFO [stdout] 4cc0877bdd083b37461d58785c0961d9ac175dbf360b9579fe71dd4a9054d206
