Nov 17 09:28:35.604 INFO testing andantonyan/24_days_of_rust against try#2e026d6e5d7621634147ad4c8074f1d964dbb1be for pr-55982
Nov 17 09:28:35.604 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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.032 INFO [stdout] 32624d513a0d91c43073a3ed7e6263e58936ed29ef58106dcbce4078614f9db7
Nov 17 09:28:36.035 INFO running `"docker" "start" "-a" "32624d513a0d91c43073a3ed7e6263e58936ed29ef58106dcbce4078614f9db7"`
Nov 17 09:28:36.815 INFO [stderr] usermod: no changes
Nov 17 09:28:36.863 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 09:28:36.863 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 09:28:36.863 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 09:28:36.863 INFO [stderr] files will be included as a binary target:
Nov 17 09:28:36.863 INFO [stderr] 
Nov 17 09:28:36.863 INFO [stderr] * /source/src/main.rs
Nov 17 09:28:36.863 INFO [stderr] 
Nov 17 09:28:36.863 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 09:28:36.863 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 09:28:36.863 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 09:28:36.863 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 09:28:36.863 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 09:28:36.863 INFO [stderr] 
Nov 17 09:28:36.863 INFO [stderr] For more information on this warning you can consult
Nov 17 09:28:36.863 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 09:28:36.903 INFO [stderr]    Compiling csv v0.15.0
Nov 17 09:28:36.903 INFO [stderr]    Compiling num-bigint v0.1.40
Nov 17 09:28:36.904 INFO [stderr]    Compiling primal-sieve v0.2.7
Nov 17 09:28:40.427 INFO [stderr]    Compiling num-rational v0.1.39
Nov 17 09:28:42.259 INFO [stderr]    Compiling num v0.1.40
Nov 17 09:28:42.711 INFO [stderr]    Compiling primal-check v0.2.2
Nov 17 09:28:43.639 INFO [stderr]    Compiling primal v0.2.3
Nov 17 09:28:44.419 INFO [stderr]    Compiling 24_days_of_rust v0.1.0 (/source)
Nov 17 09:28:46.441 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 9.59s
Nov 17 09:28:46.447 INFO [stderr] su: No module specific data is present
Nov 17 09:28:46.988 INFO running `"docker" "inspect" "32624d513a0d91c43073a3ed7e6263e58936ed29ef58106dcbce4078614f9db7"`
Nov 17 09:28:47.067 INFO running `"docker" "rm" "-f" "32624d513a0d91c43073a3ed7e6263e58936ed29ef58106dcbce4078614f9db7"`
Nov 17 09:28:47.146 INFO [stdout] 32624d513a0d91c43073a3ed7e6263e58936ed29ef58106dcbce4078614f9db7
Nov 17 09:28:47.148 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:47.306 INFO [stdout] 5f5ed1916192dc07a472947d1b0763af5d14a6f1f0e930ed591ffbe52863bc20
Nov 17 09:28:47.313 INFO running `"docker" "start" "-a" "5f5ed1916192dc07a472947d1b0763af5d14a6f1f0e930ed591ffbe52863bc20"`
Nov 17 09:28:47.897 INFO [stderr] usermod: no changes
Nov 17 09:28:47.935 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 09:28:47.937 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 09:28:47.937 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 09:28:47.937 INFO [stderr] files will be included as a binary target:
Nov 17 09:28:47.937 INFO [stderr] 
Nov 17 09:28:47.937 INFO [stderr] * /source/src/main.rs
Nov 17 09:28:47.937 INFO [stderr] 
Nov 17 09:28:47.937 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 09:28:47.937 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 09:28:47.937 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 09:28:47.937 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 09:28:47.937 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 09:28:47.937 INFO [stderr] 
Nov 17 09:28:47.937 INFO [stderr] For more information on this warning you can consult
Nov 17 09:28:47.937 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 09:28:47.959 INFO [stderr]    Compiling 24_days_of_rust v0.1.0 (/source)
Nov 17 09:28:49.138 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.21s
Nov 17 09:28:49.144 INFO [stderr] su: No module specific data is present
Nov 17 09:28:49.747 INFO running `"docker" "inspect" "5f5ed1916192dc07a472947d1b0763af5d14a6f1f0e930ed591ffbe52863bc20"`
Nov 17 09:28:49.959 INFO running `"docker" "rm" "-f" "5f5ed1916192dc07a472947d1b0763af5d14a6f1f0e930ed591ffbe52863bc20"`
Nov 17 09:28:50.253 INFO [stdout] 5f5ed1916192dc07a472947d1b0763af5d14a6f1f0e930ed591ffbe52863bc20
Nov 17 09:28:50.259 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55982/worker-5/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55982/try#2e026d6e5d7621634147ad4c8074f1d964dbb1be:/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 +2e026d6e5d7621634147ad4c8074f1d964dbb1be-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:50.524 INFO [stdout] 58aab9395d1b2db7939add46a655636e288505829aaccc69491e7aa802e2d1c2
Nov 17 09:28:50.525 INFO running `"docker" "start" "-a" "58aab9395d1b2db7939add46a655636e288505829aaccc69491e7aa802e2d1c2"`
Nov 17 09:28:51.250 INFO [stderr] usermod: no changes
Nov 17 09:28:51.299 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Nov 17 09:28:51.300 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Nov 17 09:28:51.300 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 17 09:28:51.300 INFO [stderr] files will be included as a binary target:
Nov 17 09:28:51.301 INFO [stderr] 
Nov 17 09:28:51.301 INFO [stderr] * /source/src/main.rs
Nov 17 09:28:51.301 INFO [stderr] 
Nov 17 09:28:51.302 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 17 09:28:51.302 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Nov 17 09:28:51.302 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Nov 17 09:28:51.303 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 17 09:28:51.303 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 17 09:28:51.303 INFO [stderr] 
Nov 17 09:28:51.304 INFO [stderr] For more information on this warning you can consult
Nov 17 09:28:51.304 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 17 09:28:51.333 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 0.06s
Nov 17 09:28:51.337 INFO [stderr]      Running /target/debug/deps/day2-5f4cec8bd73445d4
Nov 17 09:28:51.349 INFO [stdout] 
Nov 17 09:28:51.349 INFO [stdout] running 0 tests
Nov 17 09:28:51.349 INFO [stdout] 
Nov 17 09:28:51.350 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 09:28:51.350 INFO [stdout] 
Nov 17 09:28:51.355 INFO [stderr]      Running /target/debug/deps/day3-7ad782bdcfa8b36d
Nov 17 09:28:51.359 INFO [stderr] su: No module specific data is present
Nov 17 09:28:51.359 INFO [stdout] 
Nov 17 09:28:51.359 INFO [stdout] running 0 tests
Nov 17 09:28:51.359 INFO [stdout] 
Nov 17 09:28:51.359 INFO [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
Nov 17 09:28:51.359 INFO [stdout] 
Nov 17 09:28:51.859 INFO running `"docker" "inspect" "58aab9395d1b2db7939add46a655636e288505829aaccc69491e7aa802e2d1c2"`
Nov 17 09:28:52.028 INFO running `"docker" "rm" "-f" "58aab9395d1b2db7939add46a655636e288505829aaccc69491e7aa802e2d1c2"`
Nov 17 09:28:52.238 INFO [stdout] 58aab9395d1b2db7939add46a655636e288505829aaccc69491e7aa802e2d1c2