Dec 03 17:37:26.196 INFO testing burst-pool-0.5.1 against 1.30.1 for beta-1.31-5
Dec 03 17:37:26.196 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 17:37:26.553 INFO [stdout] eb394ef2c7aac50ffe4ff147fdb89dbf727f674887ce84f163239e6c1e17fc6c
Dec 03 17:37:26.556 INFO running `"docker" "start" "-a" "eb394ef2c7aac50ffe4ff147fdb89dbf727f674887ce84f163239e6c1e17fc6c"`
Dec 03 17:37:27.115 INFO [stderr] usermod: no changes
Dec 03 17:37:27.136 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 17:37:27.136 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 17:37:27.136 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 17:37:27.136 INFO [stderr] files will be included as a benchmark target:
Dec 03 17:37:27.136 INFO [stderr] 
Dec 03 17:37:27.136 INFO [stderr] * /source/benches/settings.rs
Dec 03 17:37:27.136 INFO [stderr] * /source/benches/stats.rs
Dec 03 17:37:27.136 INFO [stderr] 
Dec 03 17:37:27.136 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 17:37:27.136 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 17:37:27.136 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 17:37:27.136 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 17:37:27.136 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 17:37:27.136 INFO [stderr] 
Dec 03 17:37:27.136 INFO [stderr] For more information on this warning you can consult
Dec 03 17:37:27.136 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 17:37:27.159 INFO [stderr]    Compiling burst-pool v0.5.1 (/source)
Dec 03 17:37:28.186 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.06s
Dec 03 17:37:28.189 INFO [stderr] su: No module specific data is present
Dec 03 17:37:28.471 INFO running `"docker" "inspect" "eb394ef2c7aac50ffe4ff147fdb89dbf727f674887ce84f163239e6c1e17fc6c"`
Dec 03 17:37:28.527 INFO running `"docker" "rm" "-f" "eb394ef2c7aac50ffe4ff147fdb89dbf727f674887ce84f163239e6c1e17fc6c"`
Dec 03 17:37:28.597 INFO [stdout] eb394ef2c7aac50ffe4ff147fdb89dbf727f674887ce84f163239e6c1e17fc6c
Dec 03 17:37:28.599 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 17:37:28.739 INFO [stdout] adbb825d39129278f0562e68c88453e7ca367deafbdeb2febcfe53d21a8f8202
Dec 03 17:37:28.740 INFO running `"docker" "start" "-a" "adbb825d39129278f0562e68c88453e7ca367deafbdeb2febcfe53d21a8f8202"`
Dec 03 17:37:29.014 INFO [stderr] usermod: no changes
Dec 03 17:37:29.032 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 17:37:29.032 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 17:37:29.032 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 17:37:29.032 INFO [stderr] files will be included as a benchmark target:
Dec 03 17:37:29.032 INFO [stderr] 
Dec 03 17:37:29.032 INFO [stderr] * /source/benches/settings.rs
Dec 03 17:37:29.032 INFO [stderr] * /source/benches/stats.rs
Dec 03 17:37:29.032 INFO [stderr] 
Dec 03 17:37:29.032 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 17:37:29.032 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 17:37:29.032 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 17:37:29.032 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 17:37:29.032 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 17:37:29.032 INFO [stderr] 
Dec 03 17:37:29.032 INFO [stderr] For more information on this warning you can consult
Dec 03 17:37:29.032 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 17:37:29.048 INFO [stderr]    Compiling burst-pool v0.5.1 (/source)
Dec 03 17:37:30.274 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.24s
Dec 03 17:37:30.277 INFO [stderr] su: No module specific data is present
Dec 03 17:37:30.530 INFO running `"docker" "inspect" "adbb825d39129278f0562e68c88453e7ca367deafbdeb2febcfe53d21a8f8202"`
Dec 03 17:37:30.591 INFO running `"docker" "rm" "-f" "adbb825d39129278f0562e68c88453e7ca367deafbdeb2febcfe53d21a8f8202"`
Dec 03 17:37:30.647 INFO [stdout] adbb825d39129278f0562e68c88453e7ca367deafbdeb2febcfe53d21a8f8202
Dec 03 17:37:30.649 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-0/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 17:37:30.814 INFO [stdout] 922d856d382de2c00c4435dd90a265867c069093be006e55f559f635a99ed102
Dec 03 17:37:30.816 INFO running `"docker" "start" "-a" "922d856d382de2c00c4435dd90a265867c069093be006e55f559f635a99ed102"`
Dec 03 17:37:31.104 INFO [stderr] usermod: no changes
Dec 03 17:37:31.130 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 03 17:37:31.130 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 03 17:37:31.130 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 17:37:31.130 INFO [stderr] files will be included as a benchmark target:
Dec 03 17:37:31.130 INFO [stderr] 
Dec 03 17:37:31.130 INFO [stderr] * /source/benches/settings.rs
Dec 03 17:37:31.130 INFO [stderr] * /source/benches/stats.rs
Dec 03 17:37:31.130 INFO [stderr] 
Dec 03 17:37:31.130 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 17:37:31.130 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 03 17:37:31.130 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 03 17:37:31.130 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 17:37:31.130 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 17:37:31.130 INFO [stderr] 
Dec 03 17:37:31.130 INFO [stderr] For more information on this warning you can consult
Dec 03 17:37:31.130 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 17:37:31.148 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Dec 03 17:37:31.149 INFO [stderr]      Running /target/debug/deps/burst_pool-5e4eef6d88b080f5
Dec 03 17:37:31.150 INFO [stdout] 
Dec 03 17:37:31.150 INFO [stdout] running 0 tests
Dec 03 17:37:31.150 INFO [stdout] 
Dec 03 17:37:31.150 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 17:37:31.150 INFO [stdout] 
Dec 03 17:37:31.150 INFO [stderr]    Doc-tests burst_pool
Dec 03 17:37:32.489 INFO [stdout] 
Dec 03 17:37:32.489 INFO [stdout] running 1 test
Dec 03 17:37:35.430 INFO [stdout] test lib.rs -  (line 66) ... ok
Dec 03 17:37:35.430 INFO [stdout] 
Dec 03 17:37:35.430 INFO [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 17:37:35.430 INFO [stdout] 
Dec 03 17:37:35.440 INFO [stderr] su: No module specific data is present
Dec 03 17:37:36.568 INFO running `"docker" "inspect" "922d856d382de2c00c4435dd90a265867c069093be006e55f559f635a99ed102"`
Dec 03 17:37:36.798 INFO running `"docker" "rm" "-f" "922d856d382de2c00c4435dd90a265867c069093be006e55f559f635a99ed102"`
Dec 03 17:37:37.159 INFO [stdout] 922d856d382de2c00c4435dd90a265867c069093be006e55f559f635a99ed102
