[INFO] crate burst-pool 0.5.1 is already in cache
[INFO] extracting crate burst-pool 0.5.1 into work/ex/beta-1.37-6/sources/1.36.0/reg/burst-pool/0.5.1
[INFO] extracting crate burst-pool 0.5.1 into work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/burst-pool/0.5.1
[INFO] validating manifest of burst-pool-0.5.1 on toolchain 1.36.0
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of burst-pool-0.5.1 on toolchain beta-2019-07-23
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing burst-pool-0.5.1
[INFO] finished frobbing burst-pool-0.5.1
[INFO] frobbed toml for burst-pool-0.5.1 written to work/ex/beta-1.37-6/sources/1.36.0/reg/burst-pool/0.5.1/Cargo.toml
[INFO] started frobbing burst-pool-0.5.1
[INFO] finished frobbing burst-pool-0.5.1
[INFO] frobbed toml for burst-pool-0.5.1 written to work/ex/beta-1.37-6/sources/beta-2019-07-23/reg/burst-pool/0.5.1/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+1.36.0" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+beta-2019-07-23" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] testing burst-pool-0.5.1 against 1.36.0 for beta-1.37-6
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-2/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/burst-pool/0.5.1:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.36.0" "build" "--frozen"`
[INFO] [stdout] 84b12e7c73ba83689df9e480927c99f62d0a573aea2af027a604fd0584cdfe2c
[INFO] running `"docker" "start" "-a" "84b12e7c73ba83689df9e480927c99f62d0a573aea2af027a604fd0584cdfe2c"`
[INFO] [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other benchmark targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a benchmark target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/benches/stats.rs
[INFO] [stderr] * /opt/crater/workdir/benches/settings.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobenches = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr]    Compiling nix v0.9.0
[INFO] [stderr]    Compiling burst-pool v0.5.1 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.17s
[INFO] running `"docker" "inspect" "84b12e7c73ba83689df9e480927c99f62d0a573aea2af027a604fd0584cdfe2c"`
[INFO] running `"docker" "rm" "-f" "84b12e7c73ba83689df9e480927c99f62d0a573aea2af027a604fd0584cdfe2c"`
[INFO] [stdout] 84b12e7c73ba83689df9e480927c99f62d0a573aea2af027a604fd0584cdfe2c
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-2/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/burst-pool/0.5.1:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.36.0" "test" "--frozen" "--no-run"`
[INFO] [stdout] ccf359bf2eab7500917ae8c26b9f4fe84fbf7ac24b891787f88db28ba586d08f
[INFO] running `"docker" "start" "-a" "ccf359bf2eab7500917ae8c26b9f4fe84fbf7ac24b891787f88db28ba586d08f"`
[INFO] [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other benchmark targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a benchmark target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/benches/stats.rs
[INFO] [stderr] * /opt/crater/workdir/benches/settings.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobenches = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr]    Compiling spmc v0.2.2
[INFO] [stderr]    Compiling pbr v1.0.1
[INFO] [stderr]    Compiling burst-pool v0.5.1 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.11s
[INFO] running `"docker" "inspect" "ccf359bf2eab7500917ae8c26b9f4fe84fbf7ac24b891787f88db28ba586d08f"`
[INFO] running `"docker" "rm" "-f" "ccf359bf2eab7500917ae8c26b9f4fe84fbf7ac24b891787f88db28ba586d08f"`
[INFO] [stdout] ccf359bf2eab7500917ae8c26b9f4fe84fbf7ac24b891787f88db28ba586d08f
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.37-6/worker-2/1.36.0:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/beta-1.37-6/sources/1.36.0/reg/burst-pool/0.5.1:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+1.36.0" "test" "--frozen"`
[INFO] [stdout] 6b9c404dcc33008fc05652f71ecadae4fbf20c504cf70037d4de5a82227610d9
[INFO] running `"docker" "start" "-a" "6b9c404dcc33008fc05652f71ecadae4fbf20c504cf70037d4de5a82227610d9"`
[INFO] [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other benchmark targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a benchmark target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/benches/stats.rs
[INFO] [stderr] * /opt/crater/workdir/benches/settings.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobenches = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
[INFO] [stderr]      Running /opt/crater/target/debug/deps/burst_pool-7dde15ef8972f5ae
[INFO] [stdout] 
[INFO] [stdout] running 0 tests
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] [stderr]    Doc-tests burst_pool
[INFO] [stdout] 
[INFO] [stdout] running 1 test
[INFO] [stdout] test lib.rs -  (line 66) ... ok
[INFO] [stdout] 
[INFO] [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
[INFO] [stdout] 
[INFO] running `"docker" "inspect" "6b9c404dcc33008fc05652f71ecadae4fbf20c504cf70037d4de5a82227610d9"`
[INFO] running `"docker" "rm" "-f" "6b9c404dcc33008fc05652f71ecadae4fbf20c504cf70037d4de5a82227610d9"`
[INFO] [stdout] 6b9c404dcc33008fc05652f71ecadae4fbf20c504cf70037d4de5a82227610d9