Nov 02 00:09:20.570 INFO testing websession-0.8.2 against 1.30.0 for beta-1.31-1
Nov 02 00:09:20.571 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-3/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-1/1.30.0:/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.0 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"`
Nov 02 00:09:20.903 INFO blam! 296f896b4c5189512adc4dedb9ee9270abb750a8433b4386e3ba62e540e6ea4c
Nov 02 00:09:20.907 INFO running `"docker" "start" "-a" "296f896b4c5189512adc4dedb9ee9270abb750a8433b4386e3ba62e540e6ea4c"`
Nov 02 00:09:23.006 INFO kablam! usermod: no changes
Nov 02 00:09:23.067 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 00:09:23.067 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 00:09:23.067 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 00:09:23.067 INFO kablam! files will be included as a binary target:
Nov 02 00:09:23.067 INFO kablam! 
Nov 02 00:09:23.067 INFO kablam! * /source/src/bin/simple.rs
Nov 02 00:09:23.067 INFO kablam! * /source/src/bin/emit_pwhashes.rs
Nov 02 00:09:23.067 INFO kablam! 
Nov 02 00:09:23.067 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 00:09:23.067 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 00:09:23.067 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 00:09:23.067 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 00:09:23.067 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 00:09:23.067 INFO kablam! 
Nov 02 00:09:23.067 INFO kablam! For more information on this warning you can consult
Nov 02 00:09:23.067 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 00:09:23.259 INFO kablam!    Compiling rpassword v2.0.0
Nov 02 00:09:23.263 INFO kablam!    Compiling pwhash v0.2.0
Nov 02 00:09:25.874 INFO kablam!    Compiling websession v0.8.2 (/source)
Nov 02 00:09:32.407 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 9.37s
Nov 02 00:09:32.416 INFO kablam! su: No module specific data is present
Nov 02 00:09:33.716 INFO running `"docker" "rm" "-f" "296f896b4c5189512adc4dedb9ee9270abb750a8433b4386e3ba62e540e6ea4c"`
Nov 02 00:09:34.051 INFO blam! 296f896b4c5189512adc4dedb9ee9270abb750a8433b4386e3ba62e540e6ea4c
Nov 02 00:09:34.061 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-3/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-1/1.30.0:/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.0 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"`
Nov 02 00:09:34.515 INFO blam! 3410e701739f0c289c84153405f0ccb8f0268f394241b1fbfeaff3fe685b7b0b
Nov 02 00:09:34.519 INFO running `"docker" "start" "-a" "3410e701739f0c289c84153405f0ccb8f0268f394241b1fbfeaff3fe685b7b0b"`
Nov 02 00:09:35.718 INFO kablam! usermod: no changes
Nov 02 00:09:35.787 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 00:09:35.787 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 00:09:35.787 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 00:09:35.787 INFO kablam! files will be included as a binary target:
Nov 02 00:09:35.787 INFO kablam! 
Nov 02 00:09:35.787 INFO kablam! * /source/src/bin/simple.rs
Nov 02 00:09:35.787 INFO kablam! * /source/src/bin/emit_pwhashes.rs
Nov 02 00:09:35.787 INFO kablam! 
Nov 02 00:09:35.787 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 00:09:35.787 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 00:09:35.787 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 00:09:35.787 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 00:09:35.787 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 00:09:35.787 INFO kablam! 
Nov 02 00:09:35.787 INFO kablam! For more information on this warning you can consult
Nov 02 00:09:35.787 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 00:09:35.903 INFO kablam!    Compiling websession v0.8.2 (/source)
Nov 02 00:09:40.583 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 4.82s
Nov 02 00:09:40.591 INFO kablam! su: No module specific data is present
Nov 02 00:09:41.507 INFO running `"docker" "rm" "-f" "3410e701739f0c289c84153405f0ccb8f0268f394241b1fbfeaff3fe685b7b0b"`
Nov 02 00:09:41.763 INFO blam! 3410e701739f0c289c84153405f0ccb8f0268f394241b1fbfeaff3fe685b7b0b
Nov 02 00:09:41.771 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-3/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-1/1.30.0:/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.0 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"`
Nov 02 00:09:42.291 INFO blam! c692b10b9d6ca52adb4ad1e6ae3d7c09dc50c111ad3616b2b1b7ad6e37fea2f9
Nov 02 00:09:42.293 INFO running `"docker" "start" "-a" "c692b10b9d6ca52adb4ad1e6ae3d7c09dc50c111ad3616b2b1b7ad6e37fea2f9"`
Nov 02 00:09:43.679 INFO kablam! usermod: no changes
Nov 02 00:09:43.727 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 00:09:43.727 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 00:09:43.727 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 00:09:43.728 INFO kablam! files will be included as a binary target:
Nov 02 00:09:43.728 INFO kablam! 
Nov 02 00:09:43.728 INFO kablam! * /source/src/bin/simple.rs
Nov 02 00:09:43.728 INFO kablam! * /source/src/bin/emit_pwhashes.rs
Nov 02 00:09:43.728 INFO kablam! 
Nov 02 00:09:43.728 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 00:09:43.729 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 00:09:43.729 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 00:09:43.729 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 00:09:43.729 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 00:09:43.729 INFO kablam! 
Nov 02 00:09:43.729 INFO kablam! For more information on this warning you can consult
Nov 02 00:09:43.730 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 00:09:43.819 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Nov 02 00:09:43.835 INFO kablam!      Running /target/debug/deps/websession-1aea6756d38a8fb7
Nov 02 00:09:43.835 INFO blam! 
Nov 02 00:09:43.835 INFO blam! running 14 tests
Nov 02 00:09:44.199 INFO blam! test backingstore::test::fbs_can_locked_login ... ok
Nov 02 00:09:44.499 INFO blam! test backingstore::test::fbs_unicrud ... ok
Nov 02 00:09:44.631 INFO blam! test backingstore::test::fbs_check_user ... ok
Nov 02 00:09:44.751 INFO blam! test backingstore::test::mbs_can_locked_login ... ok
Nov 02 00:09:44.823 INFO blam! test backingstore::test::fbs_check_newline ... ok
Nov 02 00:09:44.983 INFO blam! test backingstore::test::mbs_check_newline2 ... ok
Nov 02 00:09:45.023 INFO blam! test backingstore::test::fbs_colons_in_usernames ... ok
Nov 02 00:09:45.071 INFO blam! test backingstore::test::fbs_create_user_plain ... ok
Nov 02 00:09:45.131 INFO blam! test backingstore::test::mbs_check_newline3 ... ok
Nov 02 00:09:45.347 INFO blam! test backingstore::test::mbs_check_newline1 ... ok
Nov 02 00:09:45.623 INFO blam! test backingstore::test::mbs_check_user ... ok
Nov 02 00:09:45.639 INFO blam! test backingstore::test::mbs_colons_in_usernames ... ok
Nov 02 00:09:45.739 INFO blam! test backingstore::test::mbs_create_user_plain ... ok
Nov 02 00:09:46.839 INFO blam! test backingstore::test::fbs_fuzz_users ... ok
Nov 02 00:09:46.839 INFO blam! 
Nov 02 00:09:46.839 INFO blam! test result: ok. 14 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 00:09:46.839 INFO blam! 
Nov 02 00:09:46.840 INFO kablam!      Running /target/debug/deps/ws_mgr-84187b954b3d3c63
Nov 02 00:09:46.846 INFO blam! 
Nov 02 00:09:46.846 INFO blam! running 0 tests
Nov 02 00:09:46.846 INFO blam! 
Nov 02 00:09:46.846 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 00:09:46.846 INFO blam! 
Nov 02 00:09:46.847 INFO kablam!    Doc-tests websession
Nov 02 00:09:48.207 INFO blam! 
Nov 02 00:09:48.207 INFO blam! running 0 tests
Nov 02 00:09:48.208 INFO blam! 
Nov 02 00:09:48.208 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 00:09:48.208 INFO blam! 
Nov 02 00:09:48.219 INFO kablam! su: No module specific data is present
Nov 02 00:09:48.982 INFO running `"docker" "rm" "-f" "c692b10b9d6ca52adb4ad1e6ae3d7c09dc50c111ad3616b2b1b7ad6e37fea2f9"`
Nov 02 00:09:49.327 INFO blam! c692b10b9d6ca52adb4ad1e6ae3d7c09dc50c111ad3616b2b1b7ad6e37fea2f9
