Nov 01 02:47:01.356 INFO testing mmstick/permutate against 1.30.0 for beta-1.31-1
Nov 01 02:47:01.357 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 01 02:47:01.847 INFO blam! 7cfa6ba036055a1ee6cfb048aded4cc4d5507c8e8d862fede5a391b99920d11b
Nov 01 02:47:01.849 INFO running `"docker" "start" "-a" "7cfa6ba036055a1ee6cfb048aded4cc4d5507c8e8d862fede5a391b99920d11b"`
Nov 01 02:47:04.106 INFO kablam! usermod: no changes
Nov 01 02:47:04.153 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 01 02:47:04.153 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 01 02:47:04.153 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 02:47:04.153 INFO kablam! files will be included as a binary target:
Nov 01 02:47:04.153 INFO kablam! 
Nov 01 02:47:04.153 INFO kablam! * /source/src/bin/arguments.rs
Nov 01 02:47:04.153 INFO kablam! * /source/src/bin/man.rs
Nov 01 02:47:04.153 INFO kablam! * /source/src/bin/buffer.rs
Nov 01 02:47:04.153 INFO kablam! 
Nov 01 02:47:04.153 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 02:47:04.153 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 01 02:47:04.153 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 01 02:47:04.153 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 02:47:04.153 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 02:47:04.153 INFO kablam! 
Nov 01 02:47:04.153 INFO kablam! For more information on this warning you can consult
Nov 01 02:47:04.153 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 02:47:04.158 INFO kablam!    Compiling permutate v0.3.2 (/source)
Nov 01 02:47:06.780 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.65s
Nov 01 02:47:06.795 INFO kablam! su: No module specific data is present
Nov 01 02:47:07.446 INFO running `"docker" "rm" "-f" "7cfa6ba036055a1ee6cfb048aded4cc4d5507c8e8d862fede5a391b99920d11b"`
Nov 01 02:47:07.908 INFO blam! 7cfa6ba036055a1ee6cfb048aded4cc4d5507c8e8d862fede5a391b99920d11b
Nov 01 02:47:07.909 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 01 02:47:08.375 INFO blam! fbf423255fa5f10314fabe80842b011dc9eabe51794458d97b01ba21626d9006
Nov 01 02:47:08.381 INFO running `"docker" "start" "-a" "fbf423255fa5f10314fabe80842b011dc9eabe51794458d97b01ba21626d9006"`
Nov 01 02:47:09.895 INFO kablam! usermod: no changes
Nov 01 02:47:09.975 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 01 02:47:09.975 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 01 02:47:09.975 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 02:47:09.975 INFO kablam! files will be included as a binary target:
Nov 01 02:47:09.975 INFO kablam! 
Nov 01 02:47:09.975 INFO kablam! * /source/src/bin/arguments.rs
Nov 01 02:47:09.975 INFO kablam! * /source/src/bin/man.rs
Nov 01 02:47:09.975 INFO kablam! * /source/src/bin/buffer.rs
Nov 01 02:47:09.975 INFO kablam! 
Nov 01 02:47:09.975 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 02:47:09.975 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 01 02:47:09.975 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 01 02:47:09.975 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 02:47:09.975 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 02:47:09.975 INFO kablam! 
Nov 01 02:47:09.975 INFO kablam! For more information on this warning you can consult
Nov 01 02:47:09.975 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 02:47:09.999 INFO kablam!    Compiling permutate v0.3.2 (/source)
Nov 01 02:47:12.985 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 3.04s
Nov 01 02:47:12.985 INFO kablam! su: No module specific data is present
Nov 01 02:47:13.493 INFO running `"docker" "rm" "-f" "fbf423255fa5f10314fabe80842b011dc9eabe51794458d97b01ba21626d9006"`
Nov 01 02:47:13.643 INFO blam! fbf423255fa5f10314fabe80842b011dc9eabe51794458d97b01ba21626d9006
Nov 01 02:47:13.645 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 01 02:47:13.868 INFO blam! 0609fe6a4ca2374e57eda2f9b4ef06c85519f76803235f22b9e674cafba12ed6
Nov 01 02:47:13.875 INFO running `"docker" "start" "-a" "0609fe6a4ca2374e57eda2f9b4ef06c85519f76803235f22b9e674cafba12ed6"`
Nov 01 02:47:14.871 INFO kablam! usermod: no changes
Nov 01 02:47:14.900 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 01 02:47:14.901 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 01 02:47:14.901 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 02:47:14.901 INFO kablam! files will be included as a binary target:
Nov 01 02:47:14.901 INFO kablam! 
Nov 01 02:47:14.901 INFO kablam! * /source/src/bin/arguments.rs
Nov 01 02:47:14.901 INFO kablam! * /source/src/bin/man.rs
Nov 01 02:47:14.901 INFO kablam! * /source/src/bin/buffer.rs
Nov 01 02:47:14.901 INFO kablam! 
Nov 01 02:47:14.901 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 02:47:14.901 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 01 02:47:14.901 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 01 02:47:14.901 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 02:47:14.902 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 02:47:14.902 INFO kablam! 
Nov 01 02:47:14.902 INFO kablam! For more information on this warning you can consult
Nov 01 02:47:14.902 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 02:47:14.902 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.01s
Nov 01 02:47:14.902 INFO kablam!      Running /target/debug/deps/permutate-1222e0394b0188a5
Nov 01 02:47:14.914 INFO blam! 
Nov 01 02:47:14.914 INFO blam! running 4 tests
Nov 01 02:47:14.914 INFO blam! test test::single_list_permutation ... ok
Nov 01 02:47:14.935 INFO blam! test test::test_reset ... ok
Nov 01 02:47:14.935 INFO blam! test test::test_permutation_values ... ok
Nov 01 02:47:16.643 INFO blam! test test::test_million_permutations ... ok
Nov 01 02:47:16.643 INFO blam! 
Nov 01 02:47:16.644 INFO blam! test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 01 02:47:16.644 INFO blam! 
Nov 01 02:47:16.647 INFO kablam!      Running /target/debug/deps/permutate-b84613414fcb83c2
Nov 01 02:47:16.649 INFO blam! 
Nov 01 02:47:16.649 INFO blam! running 1 test
Nov 01 02:47:16.649 INFO kablam!    Doc-tests permutate
Nov 01 02:47:16.650 INFO blam! test arguments::test::test_parse_arguments ... ok
Nov 01 02:47:16.650 INFO blam! 
Nov 01 02:47:16.650 INFO blam! test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 01 02:47:16.650 INFO blam! 
Nov 01 02:47:17.137 INFO blam! 
Nov 01 02:47:17.137 INFO blam! running 3 tests
Nov 01 02:47:20.167 INFO blam! test src/lib.rs -  (line 87) ... ok
Nov 01 02:47:20.181 INFO blam! test src/lib.rs -  (line 22) ... ok
Nov 01 02:47:20.349 INFO blam! test src/lib.rs -  (line 51) ... ok
Nov 01 02:47:20.350 INFO blam! 
Nov 01 02:47:20.350 INFO blam! test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 01 02:47:20.350 INFO blam! 
Nov 01 02:47:20.387 INFO kablam! su: No module specific data is present
Nov 01 02:47:21.922 INFO running `"docker" "rm" "-f" "0609fe6a4ca2374e57eda2f9b4ef06c85519f76803235f22b9e674cafba12ed6"`
Nov 01 02:47:22.299 INFO blam! 0609fe6a4ca2374e57eda2f9b4ef06c85519f76803235f22b9e674cafba12ed6
