Dec 07 22:04:36.377 INFO testing burst-pool-0.5.1 against try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468 for pr-56514 Dec 07 22:04:36.377 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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"` Dec 07 22:04:36.717 INFO [stdout] 20e4490695cbad5de11a2356bc84f18a01c315be167f42645be89e737ad718f9 Dec 07 22:04:36.726 INFO running `"docker" "start" "-a" "20e4490695cbad5de11a2356bc84f18a01c315be167f42645be89e737ad718f9"` Dec 07 22:04:37.892 INFO [stderr] usermod: no changes Dec 07 22:04:37.928 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently Dec 07 22:04:37.928 INFO [stderr] disables Cargo from automatically inferring other benchmark targets. Dec 07 22:04:37.928 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 22:04:37.928 INFO [stderr] files will be included as a benchmark target: Dec 07 22:04:37.928 INFO [stderr] Dec 07 22:04:37.928 INFO [stderr] * /source/benches/settings.rs Dec 07 22:04:37.928 INFO [stderr] * /source/benches/stats.rs Dec 07 22:04:37.928 INFO [stderr] Dec 07 22:04:37.928 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 22:04:37.928 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself Dec 07 22:04:37.928 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package] Dec 07 22:04:37.928 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 22:04:37.928 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 22:04:37.928 INFO [stderr] Dec 07 22:04:37.928 INFO [stderr] For more information on this warning you can consult Dec 07 22:04:37.928 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 22:04:37.964 INFO [stderr] Compiling burst-pool v0.5.1 (/source) Dec 07 22:04:38.808 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.91s Dec 07 22:04:38.820 INFO [stderr] su: No module specific data is present Dec 07 22:04:39.925 INFO running `"docker" "inspect" "20e4490695cbad5de11a2356bc84f18a01c315be167f42645be89e737ad718f9"` Dec 07 22:04:40.208 INFO running `"docker" "rm" "-f" "20e4490695cbad5de11a2356bc84f18a01c315be167f42645be89e737ad718f9"` Dec 07 22:04:40.492 INFO [stdout] 20e4490695cbad5de11a2356bc84f18a01c315be167f42645be89e737ad718f9 Dec 07 22:04:40.494 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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"` Dec 07 22:04:40.932 INFO [stdout] 3daac6695ac51a6145297fa52d5f8b1d02f512b6d8a2b02456fadfefb8a35e5b Dec 07 22:04:40.934 INFO running `"docker" "start" "-a" "3daac6695ac51a6145297fa52d5f8b1d02f512b6d8a2b02456fadfefb8a35e5b"` Dec 07 22:04:42.968 INFO [stderr] usermod: no changes Dec 07 22:04:43.016 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently Dec 07 22:04:43.016 INFO [stderr] disables Cargo from automatically inferring other benchmark targets. Dec 07 22:04:43.016 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 22:04:43.016 INFO [stderr] files will be included as a benchmark target: Dec 07 22:04:43.016 INFO [stderr] Dec 07 22:04:43.016 INFO [stderr] * /source/benches/settings.rs Dec 07 22:04:43.016 INFO [stderr] * /source/benches/stats.rs Dec 07 22:04:43.016 INFO [stderr] Dec 07 22:04:43.016 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 22:04:43.016 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself Dec 07 22:04:43.016 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package] Dec 07 22:04:43.016 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 22:04:43.016 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 22:04:43.016 INFO [stderr] Dec 07 22:04:43.016 INFO [stderr] For more information on this warning you can consult Dec 07 22:04:43.016 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 22:04:43.052 INFO [stderr] Compiling burst-pool v0.5.1 (/source) Dec 07 22:04:44.200 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.20s Dec 07 22:04:44.211 INFO [stderr] su: No module specific data is present Dec 07 22:04:44.802 INFO running `"docker" "inspect" "3daac6695ac51a6145297fa52d5f8b1d02f512b6d8a2b02456fadfefb8a35e5b"` Dec 07 22:04:45.104 INFO running `"docker" "rm" "-f" "3daac6695ac51a6145297fa52d5f8b1d02f512b6d8a2b02456fadfefb8a35e5b"` Dec 07 22:04:45.338 INFO [stdout] 3daac6695ac51a6145297fa52d5f8b1d02f512b6d8a2b02456fadfefb8a35e5b Dec 07 22:04:45.344 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56514/worker-0/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56514/try#6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468:/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 +6eb0fd3ac58f9b16bddb9924a17c3b6c156aa468-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"` Dec 07 22:04:45.913 INFO [stdout] e69fee0bc8c368a79e0260f00cc9c818e51e5f7d21a23183a63ba8bb203754bd Dec 07 22:04:45.916 INFO running `"docker" "start" "-a" "e69fee0bc8c368a79e0260f00cc9c818e51e5f7d21a23183a63ba8bb203754bd"` Dec 07 22:04:47.563 INFO [stderr] usermod: no changes Dec 07 22:04:47.604 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently Dec 07 22:04:47.604 INFO [stderr] disables Cargo from automatically inferring other benchmark targets. Dec 07 22:04:47.604 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 07 22:04:47.604 INFO [stderr] files will be included as a benchmark target: Dec 07 22:04:47.604 INFO [stderr] Dec 07 22:04:47.604 INFO [stderr] * /source/benches/settings.rs Dec 07 22:04:47.604 INFO [stderr] * /source/benches/stats.rs Dec 07 22:04:47.604 INFO [stderr] Dec 07 22:04:47.604 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 07 22:04:47.604 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself Dec 07 22:04:47.605 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package] Dec 07 22:04:47.605 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 07 22:04:47.605 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 07 22:04:47.605 INFO [stderr] Dec 07 22:04:47.605 INFO [stderr] For more information on this warning you can consult Dec 07 22:04:47.605 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 07 22:04:47.636 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 0.04s Dec 07 22:04:47.636 INFO [stderr] Running /target/debug/deps/burst_pool-c83b30a6d4dbcc91 Dec 07 22:04:47.638 INFO [stdout] Dec 07 22:04:47.638 INFO [stdout] running 0 tests Dec 07 22:04:47.638 INFO [stdout] Dec 07 22:04:47.638 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 22:04:47.638 INFO [stdout] Dec 07 22:04:47.638 INFO [stderr] Doc-tests burst_pool Dec 07 22:04:48.694 INFO [stdout] Dec 07 22:04:48.694 INFO [stdout] running 1 test Dec 07 22:04:50.563 INFO [stdout] test lib.rs - (line 66) ... ok Dec 07 22:04:50.563 INFO [stdout] Dec 07 22:04:50.563 INFO [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out Dec 07 22:04:50.563 INFO [stdout] Dec 07 22:04:50.580 INFO [stderr] su: No module specific data is present Dec 07 22:04:51.644 INFO running `"docker" "inspect" "e69fee0bc8c368a79e0260f00cc9c818e51e5f7d21a23183a63ba8bb203754bd"` Dec 07 22:04:51.992 INFO running `"docker" "rm" "-f" "e69fee0bc8c368a79e0260f00cc9c818e51e5f7d21a23183a63ba8bb203754bd"` Dec 07 22:04:52.268 INFO [stdout] e69fee0bc8c368a79e0260f00cc9c818e51e5f7d21a23183a63ba8bb203754bd