Nov 17 09:28:36.244 INFO testing andantonyan/24_days_of_rust against master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c for pr-55982
Nov 17 09:28:36.244 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt build --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 17 09:28:36.444 INFO [stdout] 1b77d26fda016f75a5171bc4793cacff7141e6fa94b20901a277769f1f7b9b20
Nov 17 09:28:36.448 INFO running `"docker" "start" "-a" "1b77d26fda016f75a5171bc4793cacff7141e6fa94b20901a277769f1f7b9b20"`
Nov 17 09:28:37.233 INFO [stderr] usermod: no changes
Nov 17 09:28:37.271 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 09:28:37.271 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 09:28:37.271 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 09:28:37.271 INFO [stderr] files will be included as a binary target:
Nov 17 09:28:37.271 INFO [stderr] 
Nov 17 09:28:37.271 INFO [stderr] * /source/src/main.rs
Nov 17 09:28:37.271 INFO [stderr] 
Nov 17 09:28:37.271 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 09:28:37.271 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 09:28:37.271 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 09:28:37.271 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 09:28:37.271 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 09:28:37.271 INFO [stderr] 
Nov 17 09:28:37.271 INFO [stderr] For more information on this warning you can consult
Nov 17 09:28:37.271 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 09:28:37.331 INFO [stderr]    Compiling primal-bit v0.2.4
Nov 17 09:28:37.331 INFO [stderr]    Compiling num-bigint v0.1.40
Nov 17 09:28:37.332 INFO [stderr]    Compiling csv v0.15.0
Nov 17 09:28:38.367 INFO [stderr]    Compiling primal-sieve v0.2.7
Nov 17 09:28:41.016 INFO [stderr]    Compiling num-rational v0.1.39
Nov 17 09:28:43.134 INFO [stderr]    Compiling num v0.1.40
Nov 17 09:28:43.567 INFO [stderr]    Compiling primal-check v0.2.2
Nov 17 09:28:44.462 INFO [stderr]    Compiling primal v0.2.3
Nov 17 09:28:45.387 INFO [stderr]    Compiling 24_days_of_rust v0.1.0 (/source)
Nov 17 09:28:47.141 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 9.89s
Nov 17 09:28:47.145 INFO [stderr] su: No module specific data is present
Nov 17 09:28:47.557 INFO running `"docker" "inspect" "1b77d26fda016f75a5171bc4793cacff7141e6fa94b20901a277769f1f7b9b20"`
Nov 17 09:28:47.666 INFO running `"docker" "rm" "-f" "1b77d26fda016f75a5171bc4793cacff7141e6fa94b20901a277769f1f7b9b20"`
Nov 17 09:28:47.788 INFO [stdout] 1b77d26fda016f75a5171bc4793cacff7141e6fa94b20901a277769f1f7b9b20
Nov 17 09:28:47.792 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt test --frozen --no-run" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 17 09:28:48.083 INFO [stdout] 6cec17da3a9b44c82b1b8f3690d701e624684abfb90554c7ce26c90dcc454a80
Nov 17 09:28:48.089 INFO running `"docker" "start" "-a" "6cec17da3a9b44c82b1b8f3690d701e624684abfb90554c7ce26c90dcc454a80"`
Nov 17 09:28:48.854 INFO [stderr] usermod: no changes
Nov 17 09:28:48.891 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 09:28:48.891 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 09:28:48.891 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 09:28:48.891 INFO [stderr] files will be included as a binary target:
Nov 17 09:28:48.891 INFO [stderr] 
Nov 17 09:28:48.891 INFO [stderr] * /source/src/main.rs
Nov 17 09:28:48.891 INFO [stderr] 
Nov 17 09:28:48.891 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 09:28:48.891 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 09:28:48.891 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 09:28:48.891 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 09:28:48.891 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 09:28:48.891 INFO [stderr] 
Nov 17 09:28:48.891 INFO [stderr] For more information on this warning you can consult
Nov 17 09:28:48.891 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 09:28:48.933 INFO [stderr]    Compiling 24_days_of_rust v0.1.0 (/source)
Nov 17 09:28:50.478 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.61s
Nov 17 09:28:50.483 INFO [stderr] su: No module specific data is present
Nov 17 09:28:51.027 INFO running `"docker" "inspect" "6cec17da3a9b44c82b1b8f3690d701e624684abfb90554c7ce26c90dcc454a80"`
Nov 17 09:28:51.235 INFO running `"docker" "rm" "-f" "6cec17da3a9b44c82b1b8f3690d701e624684abfb90554c7ce26c90dcc454a80"`
Nov 17 09:28:51.460 INFO [stdout] 6cec17da3a9b44c82b1b8f3690d701e624684abfb90554c7ce26c90dcc454a80
Nov 17 09:28:51.466 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-4/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55982/master#6b9b97bd9b704f85f0184f7a213cc4d62bd9654c:/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 +6b9b97bd9b704f85f0184f7a213cc4d62bd9654c-alt test --frozen" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Nov 17 09:28:51.816 INFO [stdout] 3c0c3fccc7582c87ce5886e1ec7d22bb0829077d29718eb246477cb0ef064e3b
Nov 17 09:28:51.818 INFO running `"docker" "start" "-a" "3c0c3fccc7582c87ce5886e1ec7d22bb0829077d29718eb246477cb0ef064e3b"`
Nov 17 09:28:52.450 INFO [stderr] usermod: no changes
Nov 17 09:28:52.483 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 09:28:52.484 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 09:28:52.484 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 09:28:52.484 INFO [stderr] files will be included as a binary target:
Nov 17 09:28:52.485 INFO [stderr] 
Nov 17 09:28:52.485 INFO [stderr] * /source/src/main.rs
Nov 17 09:28:52.485 INFO [stderr] 
Nov 17 09:28:52.486 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 09:28:52.486 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 09:28:52.486 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 09:28:52.487 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 09:28:52.487 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 09:28:52.487 INFO [stderr] 
Nov 17 09:28:52.487 INFO [stderr] For more information on this warning you can consult
Nov 17 09:28:52.488 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 09:28:52.507 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.03s
Nov 17 09:28:52.518 INFO [stderr]      Running /target/debug/deps/day2-38f2671d3ad4053c
Nov 17 09:28:52.523 INFO [stdout] 
Nov 17 09:28:52.523 INFO [stdout] running 0 tests
Nov 17 09:28:52.523 INFO [stdout] 
Nov 17 09:28:52.523 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 09:28:52.524 INFO [stdout] 
Nov 17 09:28:52.524 INFO [stderr]      Running /target/debug/deps/day3-9cb74baac26ad9fa
Nov 17 09:28:52.528 INFO [stdout] 
Nov 17 09:28:52.529 INFO [stdout] running 0 tests
Nov 17 09:28:52.529 INFO [stdout] 
Nov 17 09:28:52.529 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 09:28:52.529 INFO [stdout] 
Nov 17 09:28:52.531 INFO [stderr] su: No module specific data is present
Nov 17 09:28:52.848 INFO running `"docker" "inspect" "3c0c3fccc7582c87ce5886e1ec7d22bb0829077d29718eb246477cb0ef064e3b"`
Nov 17 09:28:52.973 INFO running `"docker" "rm" "-f" "3c0c3fccc7582c87ce5886e1ec7d22bb0829077d29718eb246477cb0ef064e3b"`
Nov 17 09:28:53.167 INFO [stdout] 3c0c3fccc7582c87ce5886e1ec7d22bb0829077d29718eb246477cb0ef064e3b