Nov 18 19:06:06.471 INFO testing burst-pool-0.5.1 against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 18 19:06:06.472 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 18 19:06:07.023 INFO [stdout] 32be0266295e0df7efc662ff8bd1a21d6432ce9ce7e55cb466326bc7e039c59c
Nov 18 19:06:07.027 INFO running `"docker" "start" "-a" "32be0266295e0df7efc662ff8bd1a21d6432ce9ce7e55cb466326bc7e039c59c"`
Nov 18 19:06:07.939 INFO [stderr] usermod: no changes
Nov 18 19:06:07.991 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 18 19:06:07.991 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 18 19:06:07.991 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 19:06:07.991 INFO [stderr] files will be included as a benchmark target:
Nov 18 19:06:07.991 INFO [stderr] 
Nov 18 19:06:07.991 INFO [stderr] * /source/benches/settings.rs
Nov 18 19:06:07.991 INFO [stderr] * /source/benches/stats.rs
Nov 18 19:06:07.991 INFO [stderr] 
Nov 18 19:06:07.991 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 19:06:07.991 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 18 19:06:07.991 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 18 19:06:07.991 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 19:06:07.991 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 19:06:07.991 INFO [stderr] 
Nov 18 19:06:07.991 INFO [stderr] For more information on this warning you can consult
Nov 18 19:06:07.991 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 19:06:08.039 INFO [stderr]    Compiling burst-pool v0.5.1 (/source)
Nov 18 19:06:08.931 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.97s
Nov 18 19:06:08.939 INFO [stderr] su: No module specific data is present
Nov 18 19:06:09.492 INFO running `"docker" "inspect" "32be0266295e0df7efc662ff8bd1a21d6432ce9ce7e55cb466326bc7e039c59c"`
Nov 18 19:06:09.801 INFO running `"docker" "rm" "-f" "32be0266295e0df7efc662ff8bd1a21d6432ce9ce7e55cb466326bc7e039c59c"`
Nov 18 19:06:10.036 INFO [stdout] 32be0266295e0df7efc662ff8bd1a21d6432ce9ce7e55cb466326bc7e039c59c
Nov 18 19:06:10.045 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 18 19:06:10.363 INFO [stdout] 66f03c03f9c9b85924719ca040d4bf631446e0a9afff1533302e824d0063430f
Nov 18 19:06:10.369 INFO running `"docker" "start" "-a" "66f03c03f9c9b85924719ca040d4bf631446e0a9afff1533302e824d0063430f"`
Nov 18 19:06:11.382 INFO [stderr] usermod: no changes
Nov 18 19:06:11.433 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 18 19:06:11.433 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 18 19:06:11.433 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 19:06:11.433 INFO [stderr] files will be included as a benchmark target:
Nov 18 19:06:11.433 INFO [stderr] 
Nov 18 19:06:11.433 INFO [stderr] * /source/benches/settings.rs
Nov 18 19:06:11.433 INFO [stderr] * /source/benches/stats.rs
Nov 18 19:06:11.433 INFO [stderr] 
Nov 18 19:06:11.433 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 19:06:11.433 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 18 19:06:11.433 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 18 19:06:11.433 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 19:06:11.433 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 19:06:11.433 INFO [stderr] 
Nov 18 19:06:11.433 INFO [stderr] For more information on this warning you can consult
Nov 18 19:06:11.433 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 19:06:11.471 INFO [stderr]    Compiling burst-pool v0.5.1 (/source)
Nov 18 19:06:12.686 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.27s
Nov 18 19:06:12.691 INFO [stderr] su: No module specific data is present
Nov 18 19:06:13.576 INFO running `"docker" "inspect" "66f03c03f9c9b85924719ca040d4bf631446e0a9afff1533302e824d0063430f"`
Nov 18 19:06:13.919 INFO running `"docker" "rm" "-f" "66f03c03f9c9b85924719ca040d4bf631446e0a9afff1533302e824d0063430f"`
Nov 18 19:06:14.271 INFO [stdout] 66f03c03f9c9b85924719ca040d4bf631446e0a9afff1533302e824d0063430f
Nov 18 19:06:14.276 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 18 19:06:14.700 INFO [stdout] 7df2dc69cbb2b34fa0e86df45e3054fb01201ff217571fc3928fe63925ffd871
Nov 18 19:06:14.702 INFO running `"docker" "start" "-a" "7df2dc69cbb2b34fa0e86df45e3054fb01201ff217571fc3928fe63925ffd871"`
Nov 18 19:06:16.158 INFO [stderr] usermod: no changes
Nov 18 19:06:16.227 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 18 19:06:16.227 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 18 19:06:16.227 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 18 19:06:16.227 INFO [stderr] files will be included as a benchmark target:
Nov 18 19:06:16.227 INFO [stderr] 
Nov 18 19:06:16.227 INFO [stderr] * /source/benches/settings.rs
Nov 18 19:06:16.227 INFO [stderr] * /source/benches/stats.rs
Nov 18 19:06:16.227 INFO [stderr] 
Nov 18 19:06:16.227 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 18 19:06:16.227 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 18 19:06:16.227 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 18 19:06:16.227 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 18 19:06:16.227 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 18 19:06:16.227 INFO [stderr] 
Nov 18 19:06:16.227 INFO [stderr] For more information on this warning you can consult
Nov 18 19:06:16.227 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 18 19:06:16.291 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.10s
Nov 18 19:06:16.292 INFO [stderr]      Running /target/debug/deps/burst_pool-69cfa272a4a6e9f3
Nov 18 19:06:16.294 INFO [stdout] 
Nov 18 19:06:16.294 INFO [stdout] running 0 tests
Nov 18 19:06:16.294 INFO [stdout] 
Nov 18 19:06:16.294 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 19:06:16.294 INFO [stdout] 
Nov 18 19:06:16.295 INFO [stderr]    Doc-tests burst_pool
Nov 18 19:06:17.591 INFO [stdout] 
Nov 18 19:06:17.591 INFO [stdout] running 1 test
Nov 18 19:06:19.835 INFO [stdout] test lib.rs -  (line 66) ... ok
Nov 18 19:06:19.836 INFO [stdout] 
Nov 18 19:06:19.836 INFO [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 18 19:06:19.836 INFO [stdout] 
Nov 18 19:06:19.848 INFO [stderr] su: No module specific data is present
Nov 18 19:06:21.271 INFO running `"docker" "inspect" "7df2dc69cbb2b34fa0e86df45e3054fb01201ff217571fc3928fe63925ffd871"`
Nov 18 19:06:21.636 INFO running `"docker" "rm" "-f" "7df2dc69cbb2b34fa0e86df45e3054fb01201ff217571fc3928fe63925ffd871"`
Nov 18 19:06:21.947 INFO [stdout] 7df2dc69cbb2b34fa0e86df45e3054fb01201ff217571fc3928fe63925ffd871