Nov 17 10:37:24.552 INFO testing Yatekii/rust_playground against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 17 10:37:24.553 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 17 10:37:25.108 INFO [stdout] a4a7b0b7534bcc835c4aa5e6e939c94280b79ec90204d81e3fc3c604e5c73584
Nov 17 10:37:25.110 INFO running `"docker" "start" "-a" "a4a7b0b7534bcc835c4aa5e6e939c94280b79ec90204d81e3fc3c604e5c73584"`
Nov 17 10:37:26.530 INFO [stderr] usermod: no changes
Nov 17 10:37:26.579 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 17 10:37:26.579 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 17 10:37:26.580 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 10:37:26.580 INFO [stderr] files will be included as a benchmark target:
Nov 17 10:37:26.580 INFO [stderr] 
Nov 17 10:37:26.580 INFO [stderr] * /source/benches/cell.rs
Nov 17 10:37:26.580 INFO [stderr] 
Nov 17 10:37:26.580 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 10:37:26.580 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 17 10:37:26.580 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 17 10:37:26.580 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 10:37:26.580 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 10:37:26.580 INFO [stderr] 
Nov 17 10:37:26.580 INFO [stderr] For more information on this warning you can consult
Nov 17 10:37:26.580 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 10:37:26.739 INFO [stderr]    Compiling alga v0.6.0
Nov 17 10:37:31.204 INFO [stderr]    Compiling nalgebra v0.15.3
Nov 17 10:38:03.341 INFO [stderr]    Compiling ncollide2d v0.16.1
Nov 17 10:38:11.431 INFO [stderr]    Compiling rust_playground v0.1.0 (/source)
Nov 17 10:38:13.915 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 47.35s
Nov 17 10:38:13.928 INFO [stderr] su: No module specific data is present
Nov 17 10:38:14.755 INFO running `"docker" "inspect" "a4a7b0b7534bcc835c4aa5e6e939c94280b79ec90204d81e3fc3c604e5c73584"`
Nov 17 10:38:15.021 INFO running `"docker" "rm" "-f" "a4a7b0b7534bcc835c4aa5e6e939c94280b79ec90204d81e3fc3c604e5c73584"`
Nov 17 10:38:15.407 INFO [stdout] a4a7b0b7534bcc835c4aa5e6e939c94280b79ec90204d81e3fc3c604e5c73584
Nov 17 10:38:15.411 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 17 10:38:15.920 INFO [stdout] 6796d1b2220c79f0ed04d8613eda77fef41f0f24f60060fae778b35ff9c093b3
Nov 17 10:38:15.923 INFO running `"docker" "start" "-a" "6796d1b2220c79f0ed04d8613eda77fef41f0f24f60060fae778b35ff9c093b3"`
Nov 17 10:38:17.631 INFO [stderr] usermod: no changes
Nov 17 10:38:17.683 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 17 10:38:17.683 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 17 10:38:17.683 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 10:38:17.683 INFO [stderr] files will be included as a benchmark target:
Nov 17 10:38:17.683 INFO [stderr] 
Nov 17 10:38:17.683 INFO [stderr] * /source/benches/cell.rs
Nov 17 10:38:17.683 INFO [stderr] 
Nov 17 10:38:17.683 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 10:38:17.683 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 17 10:38:17.683 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 17 10:38:17.683 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 10:38:17.683 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 10:38:17.683 INFO [stderr] 
Nov 17 10:38:17.683 INFO [stderr] For more information on this warning you can consult
Nov 17 10:38:17.683 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 10:38:17.947 INFO [stderr]    Compiling criterion-stats v0.2.3
Nov 17 10:38:17.947 INFO [stderr]    Compiling chrono v0.4.3
Nov 17 10:38:17.947 INFO [stderr]    Compiling handlebars v0.31.0
Nov 17 10:38:22.739 INFO [stderr]    Compiling simplelog v0.5.2
Nov 17 10:38:30.939 INFO [stderr]    Compiling criterion v0.2.3
Nov 17 10:38:41.811 INFO [stderr]    Compiling rust_playground v0.1.0 (/source)
Nov 17 10:38:43.187 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 25.52s
Nov 17 10:38:43.203 INFO [stderr] su: No module specific data is present
Nov 17 10:38:44.229 INFO running `"docker" "inspect" "6796d1b2220c79f0ed04d8613eda77fef41f0f24f60060fae778b35ff9c093b3"`
Nov 17 10:38:44.532 INFO running `"docker" "rm" "-f" "6796d1b2220c79f0ed04d8613eda77fef41f0f24f60060fae778b35ff9c093b3"`
Nov 17 10:38:44.837 INFO [stdout] 6796d1b2220c79f0ed04d8613eda77fef41f0f24f60060fae778b35ff9c093b3
Nov 17 10:38:44.839 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 17 10:38:45.380 INFO [stdout] 918dc7962d337a11a66b7bc67cda0634add1eaacf8a2cea77b42d4d89413db04
Nov 17 10:38:45.382 INFO running `"docker" "start" "-a" "918dc7962d337a11a66b7bc67cda0634add1eaacf8a2cea77b42d4d89413db04"`
Nov 17 10:38:47.114 INFO [stderr] usermod: no changes
Nov 17 10:38:47.168 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 17 10:38:47.168 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 17 10:38:47.168 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 10:38:47.168 INFO [stderr] files will be included as a benchmark target:
Nov 17 10:38:47.168 INFO [stderr] 
Nov 17 10:38:47.168 INFO [stderr] * /source/benches/cell.rs
Nov 17 10:38:47.168 INFO [stderr] 
Nov 17 10:38:47.168 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 10:38:47.168 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 17 10:38:47.168 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 17 10:38:47.168 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 10:38:47.168 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 10:38:47.168 INFO [stderr] 
Nov 17 10:38:47.168 INFO [stderr] For more information on this warning you can consult
Nov 17 10:38:47.168 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 10:38:47.287 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.14s
Nov 17 10:38:47.293 INFO [stderr]      Running /target/debug/deps/rust_playground-35ca18ffb2c31bde
Nov 17 10:38:47.296 INFO [stdout] 
Nov 17 10:38:47.296 INFO [stdout] running 0 tests
Nov 17 10:38:47.296 INFO [stdout] 
Nov 17 10:38:47.297 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 10:38:47.297 INFO [stdout] 
Nov 17 10:38:47.306 INFO [stderr] su: No module specific data is present
Nov 17 10:38:47.890 INFO running `"docker" "inspect" "918dc7962d337a11a66b7bc67cda0634add1eaacf8a2cea77b42d4d89413db04"`
Nov 17 10:38:48.245 INFO running `"docker" "rm" "-f" "918dc7962d337a11a66b7bc67cda0634add1eaacf8a2cea77b42d4d89413db04"`
Nov 17 10:38:48.517 INFO [stdout] 918dc7962d337a11a66b7bc67cda0634add1eaacf8a2cea77b42d4d89413db04