Nov 02 10:01:17.488 INFO testing permutate-0.3.2 against 1.30.0 for beta-1.31-1
Nov 02 10:01:17.488 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-1/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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 10:01:17.983 INFO blam! 2a56e9077afbd92aa4028476a68188f0ed8e95d1e648d167398549a3bc91eee8
Nov 02 10:01:17.985 INFO running `"docker" "start" "-a" "2a56e9077afbd92aa4028476a68188f0ed8e95d1e648d167398549a3bc91eee8"`
Nov 02 10:01:19.187 INFO kablam! usermod: no changes
Nov 02 10:01:19.263 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 10:01:19.263 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 10:01:19.263 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 10:01:19.263 INFO kablam! files will be included as a binary target:
Nov 02 10:01:19.263 INFO kablam! 
Nov 02 10:01:19.263 INFO kablam! * /source/src/bin/arguments.rs
Nov 02 10:01:19.263 INFO kablam! * /source/src/bin/man.rs
Nov 02 10:01:19.263 INFO kablam! * /source/src/bin/buffer.rs
Nov 02 10:01:19.263 INFO kablam! 
Nov 02 10:01:19.263 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 10:01:19.263 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 10:01:19.263 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 10:01:19.263 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 10:01:19.263 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 10:01:19.263 INFO kablam! 
Nov 02 10:01:19.263 INFO kablam! For more information on this warning you can consult
Nov 02 10:01:19.263 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 10:01:19.275 INFO kablam!    Compiling permutate v0.3.2 (/source)
Nov 02 10:01:22.154 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.93s
Nov 02 10:01:22.154 INFO kablam! su: No module specific data is present
Nov 02 10:01:22.819 INFO running `"docker" "rm" "-f" "2a56e9077afbd92aa4028476a68188f0ed8e95d1e648d167398549a3bc91eee8"`
Nov 02 10:01:23.083 INFO blam! 2a56e9077afbd92aa4028476a68188f0ed8e95d1e648d167398549a3bc91eee8
Nov 02 10:01:23.090 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-1/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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 10:01:23.486 INFO blam! 747654bb70dda0381450948f7dc611f2a9c16b97e102d4532c308ef8aca9fa42
Nov 02 10:01:23.499 INFO running `"docker" "start" "-a" "747654bb70dda0381450948f7dc611f2a9c16b97e102d4532c308ef8aca9fa42"`
Nov 02 10:01:24.631 INFO kablam! usermod: no changes
Nov 02 10:01:24.671 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 10:01:24.671 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 10:01:24.671 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 10:01:24.671 INFO kablam! files will be included as a binary target:
Nov 02 10:01:24.671 INFO kablam! 
Nov 02 10:01:24.671 INFO kablam! * /source/src/bin/arguments.rs
Nov 02 10:01:24.671 INFO kablam! * /source/src/bin/man.rs
Nov 02 10:01:24.671 INFO kablam! * /source/src/bin/buffer.rs
Nov 02 10:01:24.671 INFO kablam! 
Nov 02 10:01:24.671 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 10:01:24.671 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 10:01:24.671 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 10:01:24.671 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 10:01:24.671 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 10:01:24.671 INFO kablam! 
Nov 02 10:01:24.671 INFO kablam! For more information on this warning you can consult
Nov 02 10:01:24.671 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 10:01:24.675 INFO kablam!    Compiling permutate v0.3.2 (/source)
Nov 02 10:01:26.342 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.69s
Nov 02 10:01:26.345 INFO kablam! su: No module specific data is present
Nov 02 10:01:26.620 INFO running `"docker" "rm" "-f" "747654bb70dda0381450948f7dc611f2a9c16b97e102d4532c308ef8aca9fa42"`
Nov 02 10:01:26.739 INFO blam! 747654bb70dda0381450948f7dc611f2a9c16b97e102d4532c308ef8aca9fa42
Nov 02 10:01:26.747 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-1/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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 10:01:26.983 INFO blam! fe637dd455b7fafa12d1e5b1ee4cae390c04a60d27fb05bd4bc990e31492f745
Nov 02 10:01:26.991 INFO running `"docker" "start" "-a" "fe637dd455b7fafa12d1e5b1ee4cae390c04a60d27fb05bd4bc990e31492f745"`
Nov 02 10:01:27.415 INFO kablam! usermod: no changes
Nov 02 10:01:27.451 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 02 10:01:27.451 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 02 10:01:27.451 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 10:01:27.451 INFO kablam! files will be included as a binary target:
Nov 02 10:01:27.451 INFO kablam! 
Nov 02 10:01:27.451 INFO kablam! * /source/src/bin/arguments.rs
Nov 02 10:01:27.451 INFO kablam! * /source/src/bin/man.rs
Nov 02 10:01:27.451 INFO kablam! * /source/src/bin/buffer.rs
Nov 02 10:01:27.451 INFO kablam! 
Nov 02 10:01:27.451 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 10:01:27.451 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 02 10:01:27.451 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 02 10:01:27.451 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 10:01:27.451 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 10:01:27.451 INFO kablam! 
Nov 02 10:01:27.451 INFO kablam! For more information on this warning you can consult
Nov 02 10:01:27.451 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 10:01:27.456 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.01s
Nov 02 10:01:27.458 INFO kablam!      Running /target/debug/deps/permutate-1222e0394b0188a5
Nov 02 10:01:27.458 INFO blam! 
Nov 02 10:01:27.458 INFO blam! running 4 tests
Nov 02 10:01:27.459 INFO blam! test test::test_reset ... ok
Nov 02 10:01:27.463 INFO blam! test test::single_list_permutation ... ok
Nov 02 10:01:27.471 INFO blam! test test::test_permutation_values ... ok
Nov 02 10:01:28.764 INFO blam! test test::test_million_permutations ... ok
Nov 02 10:01:28.764 INFO kablam!      Running /target/debug/deps/permutate-b84613414fcb83c2
Nov 02 10:01:28.764 INFO blam! 
Nov 02 10:01:28.764 INFO blam! test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 10:01:28.764 INFO blam! 
Nov 02 10:01:28.764 INFO blam! 
Nov 02 10:01:28.764 INFO blam! running 1 test
Nov 02 10:01:28.775 INFO blam! test arguments::test::test_parse_arguments ... ok
Nov 02 10:01:28.775 INFO kablam!    Doc-tests permutate
Nov 02 10:01:28.775 INFO blam! 
Nov 02 10:01:28.775 INFO blam! test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 10:01:28.775 INFO blam! 
Nov 02 10:01:29.943 INFO blam! 
Nov 02 10:01:29.943 INFO blam! running 3 tests
Nov 02 10:01:31.638 INFO blam! test src/lib.rs -  (line 51) ... ok
Nov 02 10:01:32.019 INFO blam! test src/lib.rs -  (line 22) ... ok
Nov 02 10:01:32.075 INFO blam! test src/lib.rs -  (line 87) ... ok
Nov 02 10:01:32.075 INFO blam! 
Nov 02 10:01:32.075 INFO blam! test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 10:01:32.075 INFO blam! 
Nov 02 10:01:32.083 INFO kablam! su: No module specific data is present
Nov 02 10:01:32.796 INFO running `"docker" "rm" "-f" "fe637dd455b7fafa12d1e5b1ee4cae390c04a60d27fb05bd4bc990e31492f745"`
Nov 02 10:01:33.014 INFO blam! fe637dd455b7fafa12d1e5b1ee4cae390c04a60d27fb05bd4bc990e31492f745
