Nov 02 12:23:39.726 INFO testing metric-0.1.2 against 1.30.0 for beta-1.31-1
Nov 02 12:23:39.727 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-1/1.30.0:/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.0 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"`
Nov 02 12:23:40.164 INFO blam! 6dac8fc6dfe033e480045ab9e076866c97f9f3599606f776a9703f1afcb54489
Nov 02 12:23:40.166 INFO running `"docker" "start" "-a" "6dac8fc6dfe033e480045ab9e076866c97f9f3599606f776a9703f1afcb54489"`
Nov 02 12:23:41.929 INFO kablam! usermod: no changes
Nov 02 12:23:41.982 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 02 12:23:41.982 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 02 12:23:41.982 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 12:23:41.982 INFO kablam! files will be included as a benchmark target:
Nov 02 12:23:41.982 INFO kablam! 
Nov 02 12:23:41.982 INFO kablam! * /source/benches/nbody_raw.rs
Nov 02 12:23:41.982 INFO kablam! * /source/benches/nbody_uom.rs
Nov 02 12:23:41.982 INFO kablam! * /source/benches/nbody_metric.rs
Nov 02 12:23:41.982 INFO kablam! * /source/benches/nbody_dimensioned.rs
Nov 02 12:23:41.982 INFO kablam! 
Nov 02 12:23:41.982 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 12:23:41.982 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 02 12:23:41.982 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 02 12:23:41.982 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 12:23:41.982 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 12:23:41.982 INFO kablam! 
Nov 02 12:23:41.982 INFO kablam! For more information on this warning you can consult
Nov 02 12:23:41.982 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 12:23:42.028 INFO kablam!    Compiling metric v0.1.2 (/source)
Nov 02 12:23:47.121 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 5.16s
Nov 02 12:23:47.121 INFO kablam! su: No module specific data is present
Nov 02 12:23:47.762 INFO running `"docker" "rm" "-f" "6dac8fc6dfe033e480045ab9e076866c97f9f3599606f776a9703f1afcb54489"`
Nov 02 12:23:48.001 INFO blam! 6dac8fc6dfe033e480045ab9e076866c97f9f3599606f776a9703f1afcb54489
Nov 02 12:23:48.002 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-1/1.30.0:/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.0 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"`
Nov 02 12:23:48.463 INFO blam! 96458384b28f198f395fc0b0cb08e9595e39dd83b0e76a3c033c7777b721b0bc
Nov 02 12:23:48.475 INFO running `"docker" "start" "-a" "96458384b28f198f395fc0b0cb08e9595e39dd83b0e76a3c033c7777b721b0bc"`
Nov 02 12:23:50.203 INFO kablam! usermod: no changes
Nov 02 12:23:50.228 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 02 12:23:50.228 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 02 12:23:50.228 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 12:23:50.228 INFO kablam! files will be included as a benchmark target:
Nov 02 12:23:50.228 INFO kablam! 
Nov 02 12:23:50.228 INFO kablam! * /source/benches/nbody_raw.rs
Nov 02 12:23:50.228 INFO kablam! * /source/benches/nbody_uom.rs
Nov 02 12:23:50.228 INFO kablam! * /source/benches/nbody_metric.rs
Nov 02 12:23:50.228 INFO kablam! * /source/benches/nbody_dimensioned.rs
Nov 02 12:23:50.228 INFO kablam! 
Nov 02 12:23:50.228 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 12:23:50.228 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 02 12:23:50.228 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 02 12:23:50.228 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 12:23:50.228 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 12:23:50.228 INFO kablam! 
Nov 02 12:23:50.229 INFO kablam! For more information on this warning you can consult
Nov 02 12:23:50.229 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 12:23:50.267 INFO kablam!    Compiling dimensioned v0.6.0
Nov 02 12:23:50.275 INFO kablam!    Compiling generic-array v0.5.1
Nov 02 12:23:50.275 INFO kablam!    Compiling uom v0.14.0
Nov 02 12:24:01.007 INFO kablam!    Compiling metric v0.1.2 (/source)
Nov 02 12:24:05.547 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 15.32s
Nov 02 12:24:05.547 INFO kablam! su: No module specific data is present
Nov 02 12:24:05.932 INFO running `"docker" "rm" "-f" "96458384b28f198f395fc0b0cb08e9595e39dd83b0e76a3c033c7777b721b0bc"`
Nov 02 12:24:06.045 INFO blam! 96458384b28f198f395fc0b0cb08e9595e39dd83b0e76a3c033c7777b721b0bc
Nov 02 12:24:06.050 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-4/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/beta-1.31-1/1.30.0:/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.0 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"`
Nov 02 12:24:06.262 INFO blam! 227affd33d4262edd92f28337f874a362ff707b2cc89469a58f7ed7cb9e946ef
Nov 02 12:24:06.265 INFO running `"docker" "start" "-a" "227affd33d4262edd92f28337f874a362ff707b2cc89469a58f7ed7cb9e946ef"`
Nov 02 12:24:06.871 INFO kablam! usermod: no changes
Nov 02 12:24:06.911 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 02 12:24:06.911 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 02 12:24:06.911 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 02 12:24:06.911 INFO kablam! files will be included as a benchmark target:
Nov 02 12:24:06.911 INFO kablam! 
Nov 02 12:24:06.911 INFO kablam! * /source/benches/nbody_raw.rs
Nov 02 12:24:06.911 INFO kablam! * /source/benches/nbody_uom.rs
Nov 02 12:24:06.911 INFO kablam! * /source/benches/nbody_metric.rs
Nov 02 12:24:06.911 INFO kablam! * /source/benches/nbody_dimensioned.rs
Nov 02 12:24:06.911 INFO kablam! 
Nov 02 12:24:06.911 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 02 12:24:06.911 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 02 12:24:06.911 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 02 12:24:06.911 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 02 12:24:06.911 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 02 12:24:06.911 INFO kablam! 
Nov 02 12:24:06.911 INFO kablam! For more information on this warning you can consult
Nov 02 12:24:06.911 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 02 12:24:06.931 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.04s
Nov 02 12:24:06.937 INFO kablam!      Running /target/debug/deps/metric-7a662e4f5bb16fdf
Nov 02 12:24:06.939 INFO blam! 
Nov 02 12:24:06.939 INFO blam! running 0 tests
Nov 02 12:24:06.939 INFO blam! 
Nov 02 12:24:06.939 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 12:24:06.939 INFO blam! 
Nov 02 12:24:06.939 INFO kablam!    Doc-tests metric
Nov 02 12:24:08.207 INFO blam! 
Nov 02 12:24:08.207 INFO blam! running 0 tests
Nov 02 12:24:08.207 INFO blam! 
Nov 02 12:24:08.207 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 02 12:24:08.207 INFO blam! 
Nov 02 12:24:08.223 INFO kablam! su: No module specific data is present
Nov 02 12:24:08.715 INFO running `"docker" "rm" "-f" "227affd33d4262edd92f28337f874a362ff707b2cc89469a58f7ed7cb9e946ef"`
Nov 02 12:24:08.890 INFO blam! 227affd33d4262edd92f28337f874a362ff707b2cc89469a58f7ed7cb9e946ef
