Nov 03 01:32:08.850 INFO testing burst-pool-0.5.1 against beta-2018-10-30 for beta-1.31-1
Nov 03 01:32:08.850 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-2/beta-2018-10-30:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-1/beta-2018-10-30:/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 +beta-2018-10-30 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 03 01:32:09.267 INFO blam! fd2d8f679079d5107ae034874141d346cd33089f87780847dbcf7a3d8c2f45e1
Nov 03 01:32:09.287 INFO running `"docker" "start" "-a" "fd2d8f679079d5107ae034874141d346cd33089f87780847dbcf7a3d8c2f45e1"`
Nov 03 01:32:10.073 INFO kablam! usermod: no changes
Nov 03 01:32:10.098 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 03 01:32:10.098 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 03 01:32:10.098 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 01:32:10.098 INFO kablam! files will be included as a benchmark target:
Nov 03 01:32:10.098 INFO kablam! 
Nov 03 01:32:10.098 INFO kablam! * /source/benches/settings.rs
Nov 03 01:32:10.098 INFO kablam! * /source/benches/stats.rs
Nov 03 01:32:10.098 INFO kablam! 
Nov 03 01:32:10.098 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 01:32:10.098 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 03 01:32:10.098 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 03 01:32:10.098 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 01:32:10.098 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 01:32:10.098 INFO kablam! 
Nov 03 01:32:10.098 INFO kablam! For more information on this warning you can consult
Nov 03 01:32:10.098 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 01:32:10.119 INFO kablam!    Compiling burst-pool v0.5.1 (/source)
Nov 03 01:32:10.988 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.90s
Nov 03 01:32:10.992 INFO kablam! su: No module specific data is present
Nov 03 01:32:11.325 INFO running `"docker" "rm" "-f" "fd2d8f679079d5107ae034874141d346cd33089f87780847dbcf7a3d8c2f45e1"`
Nov 03 01:32:11.388 INFO blam! fd2d8f679079d5107ae034874141d346cd33089f87780847dbcf7a3d8c2f45e1
Nov 03 01:32:11.390 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-2/beta-2018-10-30:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-1/beta-2018-10-30:/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 +beta-2018-10-30 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 03 01:32:11.585 INFO blam! 9b8407ed959d399666dc1ce3d6a7056c515887664cf2d1f4d61992b5aa94a095
Nov 03 01:32:11.587 INFO running `"docker" "start" "-a" "9b8407ed959d399666dc1ce3d6a7056c515887664cf2d1f4d61992b5aa94a095"`
Nov 03 01:32:11.899 INFO kablam! usermod: no changes
Nov 03 01:32:11.923 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 03 01:32:11.923 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 03 01:32:11.923 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 01:32:11.923 INFO kablam! files will be included as a benchmark target:
Nov 03 01:32:11.923 INFO kablam! 
Nov 03 01:32:11.923 INFO kablam! * /source/benches/settings.rs
Nov 03 01:32:11.923 INFO kablam! * /source/benches/stats.rs
Nov 03 01:32:11.923 INFO kablam! 
Nov 03 01:32:11.923 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 01:32:11.923 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 03 01:32:11.923 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 03 01:32:11.923 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 01:32:11.923 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 01:32:11.923 INFO kablam! 
Nov 03 01:32:11.923 INFO kablam! For more information on this warning you can consult
Nov 03 01:32:11.923 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 01:32:11.936 INFO kablam!    Compiling spmc v0.2.2
Nov 03 01:32:12.416 INFO kablam!    Compiling burst-pool v0.5.1 (/source)
Nov 03 01:32:13.428 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.51s
Nov 03 01:32:13.431 INFO kablam! su: No module specific data is present
Nov 03 01:32:13.660 INFO running `"docker" "rm" "-f" "9b8407ed959d399666dc1ce3d6a7056c515887664cf2d1f4d61992b5aa94a095"`
Nov 03 01:32:13.751 INFO blam! 9b8407ed959d399666dc1ce3d6a7056c515887664cf2d1f4d61992b5aa94a095
Nov 03 01:32:13.757 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-2/beta-2018-10-30:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/beta-1.31-1/beta-2018-10-30:/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 +beta-2018-10-30 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 03 01:32:13.955 INFO blam! 8fefb3717330908f149464fdaac528d1d4e58cc6ba7b8bc397f9868507ac96bd
Nov 03 01:32:13.956 INFO running `"docker" "start" "-a" "8fefb3717330908f149464fdaac528d1d4e58cc6ba7b8bc397f9868507ac96bd"`
Nov 03 01:32:14.470 INFO kablam! usermod: no changes
Nov 03 01:32:14.489 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 03 01:32:14.489 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 03 01:32:14.489 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 01:32:14.489 INFO kablam! files will be included as a benchmark target:
Nov 03 01:32:14.489 INFO kablam! 
Nov 03 01:32:14.489 INFO kablam! * /source/benches/settings.rs
Nov 03 01:32:14.489 INFO kablam! * /source/benches/stats.rs
Nov 03 01:32:14.489 INFO kablam! 
Nov 03 01:32:14.489 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 01:32:14.489 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 03 01:32:14.489 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 03 01:32:14.489 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 01:32:14.489 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 01:32:14.489 INFO kablam! 
Nov 03 01:32:14.489 INFO kablam! For more information on this warning you can consult
Nov 03 01:32:14.489 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 01:32:14.502 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Nov 03 01:32:14.503 INFO kablam!      Running /target/debug/deps/burst_pool-b30560b1fed2f371
Nov 03 01:32:14.505 INFO blam! 
Nov 03 01:32:14.505 INFO blam! running 0 tests
Nov 03 01:32:14.505 INFO blam! 
Nov 03 01:32:14.505 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 03 01:32:14.505 INFO blam! 
Nov 03 01:32:14.506 INFO kablam!    Doc-tests burst_pool
Nov 03 01:32:15.561 INFO blam! 
Nov 03 01:32:15.561 INFO blam! running 1 test
Nov 03 01:32:17.876 INFO blam! test lib.rs -  (line 66) ... ok
Nov 03 01:32:17.876 INFO blam! 
Nov 03 01:32:17.876 INFO blam! test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 03 01:32:17.876 INFO blam! 
Nov 03 01:32:17.886 INFO kablam! su: No module specific data is present
Nov 03 01:32:18.509 INFO running `"docker" "rm" "-f" "8fefb3717330908f149464fdaac528d1d4e58cc6ba7b8bc397f9868507ac96bd"`
Nov 03 01:32:18.770 INFO blam! 8fefb3717330908f149464fdaac528d1d4e58cc6ba7b8bc397f9868507ac96bd
