Dec 01 09:55:49.199 INFO testing matthiaskrgr/advent_of_code_rs_2017 against 1.30.1 for beta-1.31-5
Dec 01 09:55:49.199 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 01 09:55:49.672 INFO [stdout] 53259b6b0c504d779735739bf4c6032c2c9a112d8921b8b7d62ab60991c06292
Dec 01 09:55:49.675 INFO running `"docker" "start" "-a" "53259b6b0c504d779735739bf4c6032c2c9a112d8921b8b7d62ab60991c06292"`
Dec 01 09:55:50.992 INFO [stderr] usermod: no changes
Dec 01 09:55:51.035 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:55:51.035 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:55:51.035 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:55:51.035 INFO [stderr] files will be included as a binary target:
Dec 01 09:55:51.035 INFO [stderr] 
Dec 01 09:55:51.035 INFO [stderr] * /source/src/main.rs
Dec 01 09:55:51.035 INFO [stderr] 
Dec 01 09:55:51.035 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:55:51.035 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:55:51.035 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:55:51.035 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:55:51.035 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:55:51.035 INFO [stderr] 
Dec 01 09:55:51.035 INFO [stderr] For more information on this warning you can consult
Dec 01 09:55:51.035 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:55:51.037 INFO [stderr]    Compiling advent_of_code_2017_rs v0.1.0 (/source)
Dec 01 09:55:53.347 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.32s
Dec 01 09:55:53.353 INFO [stderr] su: No module specific data is present
Dec 01 09:55:53.877 INFO running `"docker" "inspect" "53259b6b0c504d779735739bf4c6032c2c9a112d8921b8b7d62ab60991c06292"`
Dec 01 09:55:54.157 INFO running `"docker" "rm" "-f" "53259b6b0c504d779735739bf4c6032c2c9a112d8921b8b7d62ab60991c06292"`
Dec 01 09:55:54.379 INFO [stdout] 53259b6b0c504d779735739bf4c6032c2c9a112d8921b8b7d62ab60991c06292
Dec 01 09:55:54.381 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 01 09:55:54.769 INFO [stdout] 8fe6fb24a760285c31524ef35a3baccef5c5a96468d7c5dd4677aebc857e837b
Dec 01 09:55:54.775 INFO running `"docker" "start" "-a" "8fe6fb24a760285c31524ef35a3baccef5c5a96468d7c5dd4677aebc857e837b"`
Dec 01 09:55:55.759 INFO [stderr] usermod: no changes
Dec 01 09:55:55.807 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:55:55.807 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:55:55.807 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:55:55.807 INFO [stderr] files will be included as a binary target:
Dec 01 09:55:55.807 INFO [stderr] 
Dec 01 09:55:55.807 INFO [stderr] * /source/src/main.rs
Dec 01 09:55:55.807 INFO [stderr] 
Dec 01 09:55:55.807 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:55:55.807 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:55:55.807 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:55:55.807 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:55:55.807 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:55:55.807 INFO [stderr] 
Dec 01 09:55:55.807 INFO [stderr] For more information on this warning you can consult
Dec 01 09:55:55.807 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:55:55.820 INFO [stderr]    Compiling advent_of_code_2017_rs v0.1.0 (/source)
Dec 01 09:55:58.415 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.63s
Dec 01 09:55:58.416 INFO [stderr] su: No module specific data is present
Dec 01 09:55:59.139 INFO running `"docker" "inspect" "8fe6fb24a760285c31524ef35a3baccef5c5a96468d7c5dd4677aebc857e837b"`
Dec 01 09:55:59.325 INFO running `"docker" "rm" "-f" "8fe6fb24a760285c31524ef35a3baccef5c5a96468d7c5dd4677aebc857e837b"`
Dec 01 09:55:59.630 INFO [stdout] 8fe6fb24a760285c31524ef35a3baccef5c5a96468d7c5dd4677aebc857e837b
Dec 01 09:55:59.633 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 01 09:56:00.119 INFO [stdout] 87a2e8f4f9a4ca8774bbb607a343070b29b01b32de74956885231b54335de80b
Dec 01 09:56:00.121 INFO running `"docker" "start" "-a" "87a2e8f4f9a4ca8774bbb607a343070b29b01b32de74956885231b54335de80b"`
Dec 01 09:56:01.207 INFO [stderr] usermod: no changes
Dec 01 09:56:01.246 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 01 09:56:01.246 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 01 09:56:01.246 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 01 09:56:01.246 INFO [stderr] files will be included as a binary target:
Dec 01 09:56:01.246 INFO [stderr] 
Dec 01 09:56:01.246 INFO [stderr] * /source/src/main.rs
Dec 01 09:56:01.246 INFO [stderr] 
Dec 01 09:56:01.246 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 01 09:56:01.246 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 01 09:56:01.246 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 01 09:56:01.246 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 01 09:56:01.246 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 01 09:56:01.246 INFO [stderr] 
Dec 01 09:56:01.246 INFO [stderr] For more information on this warning you can consult
Dec 01 09:56:01.246 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 01 09:56:01.259 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.02s
Dec 01 09:56:01.263 INFO [stderr]      Running /target/debug/deps/day1_1-a60b073ca54c86ac
Dec 01 09:56:01.267 INFO [stdout] 
Dec 01 09:56:01.267 INFO [stdout] running 0 tests
Dec 01 09:56:01.267 INFO [stdout] 
Dec 01 09:56:01.267 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 09:56:01.267 INFO [stdout] 
Dec 01 09:56:01.267 INFO [stderr]      Running /target/debug/deps/day1_2-ca790c1e4502eef2
Dec 01 09:56:01.280 INFO [stdout] 
Dec 01 09:56:01.280 INFO [stdout] running 0 tests
Dec 01 09:56:01.280 INFO [stdout] 
Dec 01 09:56:01.280 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 09:56:01.280 INFO [stdout] 
Dec 01 09:56:01.280 INFO [stderr]      Running /target/debug/deps/day2_1-3718e0130d4a57ca
Dec 01 09:56:01.291 INFO [stdout] 
Dec 01 09:56:01.291 INFO [stdout] running 0 tests
Dec 01 09:56:01.291 INFO [stdout] 
Dec 01 09:56:01.291 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 09:56:01.291 INFO [stdout] 
Dec 01 09:56:01.291 INFO [stdout] 
Dec 01 09:56:01.291 INFO [stdout] running 0 tests
Dec 01 09:56:01.291 INFO [stdout] 
Dec 01 09:56:01.291 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Dec 01 09:56:01.291 INFO [stdout] 
Dec 01 09:56:01.291 INFO [stderr]      Running /target/debug/deps/day2_2-ae79958034f1244f
Dec 01 09:56:01.292 INFO [stderr] su: No module specific data is present
Dec 01 09:56:02.112 INFO running `"docker" "inspect" "87a2e8f4f9a4ca8774bbb607a343070b29b01b32de74956885231b54335de80b"`
Dec 01 09:56:02.445 INFO running `"docker" "rm" "-f" "87a2e8f4f9a4ca8774bbb607a343070b29b01b32de74956885231b54335de80b"`
Dec 01 09:56:02.719 INFO [stdout] 87a2e8f4f9a4ca8774bbb607a343070b29b01b32de74956885231b54335de80b
