Nov 03 00:03:24.154 INFO testing cli-utils-0.1.0 against 1.30.0 for beta-1.31-1
Nov 03 00:03:24.154 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-7/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 03 00:03:24.574 INFO blam! ea52e526a5187050434e509158a134353950cbea538ff5f5588efaf3245da224
Nov 03 00:03:24.574 INFO running `"docker" "start" "-a" "ea52e526a5187050434e509158a134353950cbea538ff5f5588efaf3245da224"`
Nov 03 00:03:25.266 INFO kablam! usermod: no changes
Nov 03 00:03:25.331 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 03 00:03:25.331 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 03 00:03:25.331 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 00:03:25.331 INFO kablam! files will be included as a binary target:
Nov 03 00:03:25.331 INFO kablam! 
Nov 03 00:03:25.331 INFO kablam! * /source/src/bin/execute.rs
Nov 03 00:03:25.331 INFO kablam! 
Nov 03 00:03:25.331 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 00:03:25.331 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 03 00:03:25.331 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 03 00:03:25.331 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 00:03:25.331 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 00:03:25.331 INFO kablam! 
Nov 03 00:03:25.331 INFO kablam! For more information on this warning you can consult
Nov 03 00:03:25.331 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 00:03:25.359 INFO kablam!    Compiling cli-utils v0.1.0 (/source)
Nov 03 00:03:26.855 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.55s
Nov 03 00:03:26.858 INFO kablam! su: No module specific data is present
Nov 03 00:03:27.227 INFO running `"docker" "rm" "-f" "ea52e526a5187050434e509158a134353950cbea538ff5f5588efaf3245da224"`
Nov 03 00:03:27.356 INFO blam! ea52e526a5187050434e509158a134353950cbea538ff5f5588efaf3245da224
Nov 03 00:03:27.362 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-7/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 03 00:03:27.627 INFO blam! e356c5fab5229a0df40f6335355bf331a30f52f743d2e087dfc2ef79a8c45e24
Nov 03 00:03:27.629 INFO running `"docker" "start" "-a" "e356c5fab5229a0df40f6335355bf331a30f52f743d2e087dfc2ef79a8c45e24"`
Nov 03 00:03:28.160 INFO kablam! usermod: no changes
Nov 03 00:03:28.187 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 03 00:03:28.187 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 03 00:03:28.187 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 00:03:28.187 INFO kablam! files will be included as a binary target:
Nov 03 00:03:28.187 INFO kablam! 
Nov 03 00:03:28.187 INFO kablam! * /source/src/bin/execute.rs
Nov 03 00:03:28.187 INFO kablam! 
Nov 03 00:03:28.187 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 00:03:28.187 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 03 00:03:28.187 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 03 00:03:28.187 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 00:03:28.187 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 00:03:28.187 INFO kablam! 
Nov 03 00:03:28.187 INFO kablam! For more information on this warning you can consult
Nov 03 00:03:28.187 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 00:03:28.195 INFO kablam!    Compiling cli-utils v0.1.0 (/source)
Nov 03 00:03:29.538 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.36s
Nov 03 00:03:29.540 INFO kablam! su: No module specific data is present
Nov 03 00:03:29.899 INFO running `"docker" "rm" "-f" "e356c5fab5229a0df40f6335355bf331a30f52f743d2e087dfc2ef79a8c45e24"`
Nov 03 00:03:29.999 INFO blam! e356c5fab5229a0df40f6335355bf331a30f52f743d2e087dfc2ef79a8c45e24
Nov 03 00:03:30.009 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-7/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 03 00:03:30.228 INFO blam! a68561ea119335c55f1bf8ac5995669f06de8aa5b4ea021f27862ebb243a2b90
Nov 03 00:03:30.230 INFO running `"docker" "start" "-a" "a68561ea119335c55f1bf8ac5995669f06de8aa5b4ea021f27862ebb243a2b90"`
Nov 03 00:03:30.897 INFO kablam! usermod: no changes
Nov 03 00:03:30.943 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 03 00:03:30.943 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 03 00:03:30.943 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 03 00:03:30.943 INFO kablam! files will be included as a binary target:
Nov 03 00:03:30.943 INFO kablam! 
Nov 03 00:03:30.943 INFO kablam! * /source/src/bin/execute.rs
Nov 03 00:03:30.943 INFO kablam! 
Nov 03 00:03:30.943 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 03 00:03:30.943 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 03 00:03:30.943 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 03 00:03:30.943 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 03 00:03:30.943 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 03 00:03:30.943 INFO kablam! 
Nov 03 00:03:30.943 INFO kablam! For more information on this warning you can consult
Nov 03 00:03:30.943 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 03 00:03:30.959 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.03s
Nov 03 00:03:30.967 INFO kablam!      Running /target/debug/deps/loop-804211bc9ea9860e
Nov 03 00:03:30.970 INFO blam! 
Nov 03 00:03:30.970 INFO blam! running 0 tests
Nov 03 00:03:30.970 INFO blam! 
Nov 03 00:03:30.970 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 03 00:03:30.970 INFO blam! 
Nov 03 00:03:30.970 INFO blam! 
Nov 03 00:03:30.970 INFO blam! running 0 tests
Nov 03 00:03:30.971 INFO blam! 
Nov 03 00:03:30.971 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 03 00:03:30.971 INFO blam! 
Nov 03 00:03:30.971 INFO kablam!      Running /target/debug/deps/timer-440d1cb529c3974d
Nov 03 00:03:30.973 INFO kablam! su: No module specific data is present
Nov 03 00:03:31.721 INFO running `"docker" "rm" "-f" "a68561ea119335c55f1bf8ac5995669f06de8aa5b4ea021f27862ebb243a2b90"`
Nov 03 00:03:32.015 INFO blam! a68561ea119335c55f1bf8ac5995669f06de8aa5b4ea021f27862ebb243a2b90
