Dec 03 15:55:26.588 INFO testing cli-utils-0.1.0 against 1.30.1 for beta-1.31-5
Dec 03 15:55:26.588 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 15:55:26.881 INFO [stdout] 414b36ff5d4f4b2d1ff7da3705b674dc65e7e3a99875be70fd886f95909e97c7
Dec 03 15:55:26.884 INFO running `"docker" "start" "-a" "414b36ff5d4f4b2d1ff7da3705b674dc65e7e3a99875be70fd886f95909e97c7"`
Dec 03 15:55:27.795 INFO [stderr] usermod: no changes
Dec 03 15:55:27.847 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 15:55:27.847 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 15:55:27.847 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 15:55:27.847 INFO [stderr] files will be included as a binary target:
Dec 03 15:55:27.847 INFO [stderr] 
Dec 03 15:55:27.847 INFO [stderr] * /source/src/bin/execute.rs
Dec 03 15:55:27.847 INFO [stderr] 
Dec 03 15:55:27.847 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 15:55:27.847 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 15:55:27.847 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 15:55:27.847 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 15:55:27.847 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 15:55:27.847 INFO [stderr] 
Dec 03 15:55:27.847 INFO [stderr] For more information on this warning you can consult
Dec 03 15:55:27.847 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 15:55:27.849 INFO [stderr]    Compiling cli-utils v0.1.0 (/source)
Dec 03 15:55:29.569 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.74s
Dec 03 15:55:29.572 INFO [stderr] su: No module specific data is present
Dec 03 15:55:29.956 INFO running `"docker" "inspect" "414b36ff5d4f4b2d1ff7da3705b674dc65e7e3a99875be70fd886f95909e97c7"`
Dec 03 15:55:30.083 INFO running `"docker" "rm" "-f" "414b36ff5d4f4b2d1ff7da3705b674dc65e7e3a99875be70fd886f95909e97c7"`
Dec 03 15:55:30.231 INFO [stdout] 414b36ff5d4f4b2d1ff7da3705b674dc65e7e3a99875be70fd886f95909e97c7
Dec 03 15:55:30.237 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 15:55:30.567 INFO [stdout] 8817b4b96c1505c1d1729c1f91894257405e67b1c4717d7dd1c011487a213cb4
Dec 03 15:55:30.569 INFO running `"docker" "start" "-a" "8817b4b96c1505c1d1729c1f91894257405e67b1c4717d7dd1c011487a213cb4"`
Dec 03 15:55:31.739 INFO [stderr] usermod: no changes
Dec 03 15:55:31.787 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 15:55:31.787 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 15:55:31.787 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 15:55:31.787 INFO [stderr] files will be included as a binary target:
Dec 03 15:55:31.787 INFO [stderr] 
Dec 03 15:55:31.787 INFO [stderr] * /source/src/bin/execute.rs
Dec 03 15:55:31.787 INFO [stderr] 
Dec 03 15:55:31.787 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 15:55:31.787 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 15:55:31.787 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 15:55:31.787 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 15:55:31.787 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 15:55:31.787 INFO [stderr] 
Dec 03 15:55:31.787 INFO [stderr] For more information on this warning you can consult
Dec 03 15:55:31.787 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 15:55:31.799 INFO [stderr]    Compiling cli-utils v0.1.0 (/source)
Dec 03 15:55:34.131 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.36s
Dec 03 15:55:34.131 INFO [stderr] su: No module specific data is present
Dec 03 15:55:35.065 INFO running `"docker" "inspect" "8817b4b96c1505c1d1729c1f91894257405e67b1c4717d7dd1c011487a213cb4"`
Dec 03 15:55:35.307 INFO running `"docker" "rm" "-f" "8817b4b96c1505c1d1729c1f91894257405e67b1c4717d7dd1c011487a213cb4"`
Dec 03 15:55:35.555 INFO [stdout] 8817b4b96c1505c1d1729c1f91894257405e67b1c4717d7dd1c011487a213cb4
Dec 03 15:55:35.563 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-5/worker-3/1.30.1:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/beta-1.31-5/1.30.1:/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.1 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"`
Dec 03 15:55:36.203 INFO [stdout] 82449a6d42ce0817b02f0d04fdde0edddf993f041a8b265306cbec5426b7f33b
Dec 03 15:55:36.205 INFO running `"docker" "start" "-a" "82449a6d42ce0817b02f0d04fdde0edddf993f041a8b265306cbec5426b7f33b"`
Dec 03 15:55:37.426 INFO [stderr] usermod: no changes
Dec 03 15:55:37.467 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 03 15:55:37.467 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 03 15:55:37.467 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 03 15:55:37.467 INFO [stderr] files will be included as a binary target:
Dec 03 15:55:37.467 INFO [stderr] 
Dec 03 15:55:37.467 INFO [stderr] * /source/src/bin/execute.rs
Dec 03 15:55:37.467 INFO [stderr] 
Dec 03 15:55:37.467 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 03 15:55:37.467 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 03 15:55:37.467 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 03 15:55:37.467 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 03 15:55:37.467 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 03 15:55:37.467 INFO [stderr] 
Dec 03 15:55:37.467 INFO [stderr] For more information on this warning you can consult
Dec 03 15:55:37.467 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 03 15:55:37.495 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.05s
Dec 03 15:55:37.499 INFO [stderr]      Running /target/debug/deps/loop-1d0cf141e0d5cd48
Dec 03 15:55:37.503 INFO [stdout] 
Dec 03 15:55:37.503 INFO [stdout] running 0 tests
Dec 03 15:55:37.503 INFO [stdout] 
Dec 03 15:55:37.503 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 15:55:37.503 INFO [stdout] 
Dec 03 15:55:37.503 INFO [stderr]      Running /target/debug/deps/timer-27ed7a94087c13b0
Dec 03 15:55:37.505 INFO [stdout] 
Dec 03 15:55:37.505 INFO [stdout] running 0 tests
Dec 03 15:55:37.505 INFO [stdout] 
Dec 03 15:55:37.505 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 03 15:55:37.505 INFO [stdout] 
Dec 03 15:55:37.506 INFO [stderr] su: No module specific data is present
Dec 03 15:55:38.389 INFO running `"docker" "inspect" "82449a6d42ce0817b02f0d04fdde0edddf993f041a8b265306cbec5426b7f33b"`
Dec 03 15:55:38.648 INFO running `"docker" "rm" "-f" "82449a6d42ce0817b02f0d04fdde0edddf993f041a8b265306cbec5426b7f33b"`
Dec 03 15:55:38.843 INFO [stdout] 82449a6d42ce0817b02f0d04fdde0edddf993f041a8b265306cbec5426b7f33b
