Nov 03 01:32:10.621 INFO testing burst-pool-0.5.1 against 1.30.0 for beta-1.31-1
Nov 03 01:32:10.621 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-0/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 03 01:32:10.887 INFO blam! a18e030e42f3a472dc19ac1b314dc4d6df4561d83094251e95bf644bb0491618
Nov 03 01:32:10.890 INFO running `"docker" "start" "-a" "a18e030e42f3a472dc19ac1b314dc4d6df4561d83094251e95bf644bb0491618"`
Nov 03 01:32:11.336 INFO kablam! usermod: no changes
Nov 03 01:32:11.357 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 03 01:32:11.357 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 03 01:32:11.357 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 01:32:11.357 INFO kablam! files will be included as a benchmark target:
Nov 03 01:32:11.357 INFO kablam! 
Nov 03 01:32:11.357 INFO kablam! * /source/benches/settings.rs
Nov 03 01:32:11.357 INFO kablam! * /source/benches/stats.rs
Nov 03 01:32:11.357 INFO kablam! 
Nov 03 01:32:11.357 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 01:32:11.357 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 03 01:32:11.357 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 03 01:32:11.357 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 01:32:11.357 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 01:32:11.358 INFO kablam! 
Nov 03 01:32:11.358 INFO kablam! For more information on this warning you can consult
Nov 03 01:32:11.358 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 01:32:11.379 INFO kablam!    Compiling burst-pool v0.5.1 (/source)
Nov 03 01:32:12.209 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.86s
Nov 03 01:32:12.213 INFO kablam! su: No module specific data is present
Nov 03 01:32:12.424 INFO running `"docker" "rm" "-f" "a18e030e42f3a472dc19ac1b314dc4d6df4561d83094251e95bf644bb0491618"`
Nov 03 01:32:12.490 INFO blam! a18e030e42f3a472dc19ac1b314dc4d6df4561d83094251e95bf644bb0491618
Nov 03 01:32:12.490 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-0/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 03 01:32:12.650 INFO blam! 22c62c1aa6e4248adc1f1c16306c46e35e79507bce94e7c8755cff4c09f48a20
Nov 03 01:32:12.652 INFO running `"docker" "start" "-a" "22c62c1aa6e4248adc1f1c16306c46e35e79507bce94e7c8755cff4c09f48a20"`
Nov 03 01:32:12.958 INFO kablam! usermod: no changes
Nov 03 01:32:12.981 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 03 01:32:12.981 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 03 01:32:12.981 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 01:32:12.982 INFO kablam! files will be included as a benchmark target:
Nov 03 01:32:12.982 INFO kablam! 
Nov 03 01:32:12.982 INFO kablam! * /source/benches/settings.rs
Nov 03 01:32:12.983 INFO kablam! * /source/benches/stats.rs
Nov 03 01:32:12.983 INFO kablam! 
Nov 03 01:32:12.983 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 01:32:12.984 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 03 01:32:12.984 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 03 01:32:12.984 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 01:32:12.984 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 01:32:12.985 INFO kablam! 
Nov 03 01:32:12.985 INFO kablam! For more information on this warning you can consult
Nov 03 01:32:12.985 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 01:32:12.997 INFO kablam!    Compiling burst-pool v0.5.1 (/source)
Nov 03 01:32:14.106 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.13s
Nov 03 01:32:14.108 INFO kablam! su: No module specific data is present
Nov 03 01:32:14.328 INFO running `"docker" "rm" "-f" "22c62c1aa6e4248adc1f1c16306c46e35e79507bce94e7c8755cff4c09f48a20"`
Nov 03 01:32:14.386 INFO blam! 22c62c1aa6e4248adc1f1c16306c46e35e79507bce94e7c8755cff4c09f48a20
Nov 03 01:32:14.388 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-0/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 03 01:32:14.523 INFO blam! 251dbb81b20976efc0887d36ed4c11f59abed5038927b06b5308506c5c2f6ea6
Nov 03 01:32:14.525 INFO running `"docker" "start" "-a" "251dbb81b20976efc0887d36ed4c11f59abed5038927b06b5308506c5c2f6ea6"`
Nov 03 01:32:14.840 INFO kablam! usermod: no changes
Nov 03 01:32:14.863 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 03 01:32:14.863 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 03 01:32:14.863 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 01:32:14.863 INFO kablam! files will be included as a benchmark target:
Nov 03 01:32:14.863 INFO kablam! 
Nov 03 01:32:14.863 INFO kablam! * /source/benches/settings.rs
Nov 03 01:32:14.863 INFO kablam! * /source/benches/stats.rs
Nov 03 01:32:14.863 INFO kablam! 
Nov 03 01:32:14.863 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 01:32:14.863 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 03 01:32:14.863 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 03 01:32:14.863 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 01:32:14.863 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 01:32:14.863 INFO kablam! 
Nov 03 01:32:14.863 INFO kablam! For more information on this warning you can consult
Nov 03 01:32:14.863 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 01:32:14.881 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Nov 03 01:32:14.882 INFO kablam!      Running /target/debug/deps/burst_pool-b4cd280893a1e536
Nov 03 01:32:14.884 INFO blam! 
Nov 03 01:32:14.884 INFO blam! running 0 tests
Nov 03 01:32:14.884 INFO blam! 
Nov 03 01:32:14.884 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 03 01:32:14.884 INFO blam! 
Nov 03 01:32:14.884 INFO kablam!    Doc-tests burst_pool
Nov 03 01:32:16.522 INFO blam! 
Nov 03 01:32:16.522 INFO blam! running 1 test
Nov 03 01:32:19.195 INFO blam! test lib.rs -  (line 66) ... ok
Nov 03 01:32:19.195 INFO blam! 
Nov 03 01:32:19.195 INFO blam! test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 03 01:32:19.195 INFO blam! 
Nov 03 01:32:19.215 INFO kablam! su: No module specific data is present
Nov 03 01:32:19.960 INFO running `"docker" "rm" "-f" "251dbb81b20976efc0887d36ed4c11f59abed5038927b06b5308506c5c2f6ea6"`
Nov 03 01:32:20.303 INFO blam! 251dbb81b20976efc0887d36ed4c11f59abed5038927b06b5308506c5c2f6ea6
