Nov 01 03:33:17.129 INFO testing matthiaskrgr/advent_of_code_rs_2017 against 1.30.0 for beta-1.31-1
Nov 01 03:33:17.131 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-2/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 01 03:33:17.486 INFO blam! 5198c032eb4bb06d29517e988779cdbc5320784ccadefe0ad7e9b8087653cd25
Nov 01 03:33:17.491 INFO running `"docker" "start" "-a" "5198c032eb4bb06d29517e988779cdbc5320784ccadefe0ad7e9b8087653cd25"`
Nov 01 03:33:18.489 INFO kablam! usermod: no changes
Nov 01 03:33:18.586 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 01 03:33:18.586 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 01 03:33:18.586 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 03:33:18.586 INFO kablam! files will be included as a binary target:
Nov 01 03:33:18.586 INFO kablam! 
Nov 01 03:33:18.586 INFO kablam! * /source/src/main.rs
Nov 01 03:33:18.586 INFO kablam! 
Nov 01 03:33:18.586 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 03:33:18.586 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 01 03:33:18.586 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 01 03:33:18.586 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 03:33:18.586 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 03:33:18.586 INFO kablam! 
Nov 01 03:33:18.586 INFO kablam! For more information on this warning you can consult
Nov 01 03:33:18.586 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 03:33:18.591 INFO kablam!    Compiling advent_of_code_2017_rs v0.1.0 (/source)
Nov 01 03:33:20.419 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.89s
Nov 01 03:33:20.421 INFO kablam! su: No module specific data is present
Nov 01 03:33:20.822 INFO running `"docker" "rm" "-f" "5198c032eb4bb06d29517e988779cdbc5320784ccadefe0ad7e9b8087653cd25"`
Nov 01 03:33:21.073 INFO blam! 5198c032eb4bb06d29517e988779cdbc5320784ccadefe0ad7e9b8087653cd25
Nov 01 03:33:21.076 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-2/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 01 03:33:21.464 INFO blam! 046a7273afe9e189fbc249784be1fe563da258b293a657aa1ab7c7167faa1c34
Nov 01 03:33:21.467 INFO running `"docker" "start" "-a" "046a7273afe9e189fbc249784be1fe563da258b293a657aa1ab7c7167faa1c34"`
Nov 01 03:33:21.906 INFO kablam! usermod: no changes
Nov 01 03:33:21.931 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 01 03:33:21.931 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 01 03:33:21.931 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 03:33:21.931 INFO kablam! files will be included as a binary target:
Nov 01 03:33:21.931 INFO kablam! 
Nov 01 03:33:21.931 INFO kablam! * /source/src/main.rs
Nov 01 03:33:21.931 INFO kablam! 
Nov 01 03:33:21.931 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 03:33:21.931 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 01 03:33:21.931 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 01 03:33:21.931 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 03:33:21.931 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 03:33:21.931 INFO kablam! 
Nov 01 03:33:21.931 INFO kablam! For more information on this warning you can consult
Nov 01 03:33:21.931 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 03:33:21.933 INFO kablam!    Compiling advent_of_code_2017_rs v0.1.0 (/source)
Nov 01 03:33:22.948 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.02s
Nov 01 03:33:22.949 INFO kablam! su: No module specific data is present
Nov 01 03:33:23.471 INFO running `"docker" "rm" "-f" "046a7273afe9e189fbc249784be1fe563da258b293a657aa1ab7c7167faa1c34"`
Nov 01 03:33:23.655 INFO blam! 046a7273afe9e189fbc249784be1fe563da258b293a657aa1ab7c7167faa1c34
Nov 01 03:33:23.661 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/beta-1.31-1/worker-2/1.30.0:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/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 01 03:33:23.973 INFO blam! 064089922d440a1ab5164956ef208bc6547448ec2f65a69b005db5b940cb67c2
Nov 01 03:33:23.976 INFO running `"docker" "start" "-a" "064089922d440a1ab5164956ef208bc6547448ec2f65a69b005db5b940cb67c2"`
Nov 01 03:33:24.851 INFO kablam! usermod: no changes
Nov 01 03:33:24.891 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 01 03:33:24.891 INFO kablam! disables Cargo from automatically inferring other binary targets.
Nov 01 03:33:24.891 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 03:33:24.891 INFO kablam! files will be included as a binary target:
Nov 01 03:33:24.891 INFO kablam! 
Nov 01 03:33:24.891 INFO kablam! * /source/src/main.rs
Nov 01 03:33:24.891 INFO kablam! 
Nov 01 03:33:24.891 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 03:33:24.891 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Nov 01 03:33:24.891 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Nov 01 03:33:24.891 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 03:33:24.891 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 03:33:24.891 INFO kablam! 
Nov 01 03:33:24.891 INFO kablam! For more information on this warning you can consult
Nov 01 03:33:24.891 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 03:33:24.891 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 0.01s
Nov 01 03:33:24.899 INFO kablam!      Running /target/debug/deps/day1_1-0d7f38886aa4d371
Nov 01 03:33:24.907 INFO blam! 
Nov 01 03:33:24.909 INFO kablam!      Running /target/debug/deps/day1_2-489c2f44ff0f08bd
Nov 01 03:33:24.909 INFO blam! running 0 tests
Nov 01 03:33:24.909 INFO blam! 
Nov 01 03:33:24.909 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 01 03:33:24.909 INFO blam! 
Nov 01 03:33:24.910 INFO blam! 
Nov 01 03:33:24.910 INFO blam! running 0 tests
Nov 01 03:33:24.910 INFO blam! 
Nov 01 03:33:24.910 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 01 03:33:24.910 INFO blam! 
Nov 01 03:33:24.911 INFO kablam!      Running /target/debug/deps/day2_1-4d50792b27e8f94a
Nov 01 03:33:24.919 INFO kablam!      Running /target/debug/deps/day2_2-0f4a0d594864e79c
Nov 01 03:33:24.919 INFO blam! 
Nov 01 03:33:24.919 INFO blam! running 0 tests
Nov 01 03:33:24.919 INFO blam! 
Nov 01 03:33:24.919 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 01 03:33:24.919 INFO blam! 
Nov 01 03:33:24.919 INFO blam! 
Nov 01 03:33:24.919 INFO blam! running 0 tests
Nov 01 03:33:24.919 INFO blam! 
Nov 01 03:33:24.919 INFO blam! test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 01 03:33:24.919 INFO blam! 
Nov 01 03:33:24.923 INFO kablam! su: No module specific data is present
Nov 01 03:33:25.591 INFO running `"docker" "rm" "-f" "064089922d440a1ab5164956ef208bc6547448ec2f65a69b005db5b940cb67c2"`
Nov 01 03:33:25.835 INFO blam! 064089922d440a1ab5164956ef208bc6547448ec2f65a69b005db5b940cb67c2
