Dec 05 04:48:19.136 INFO checking usi-run-0.5.0 against master#c8ae2de8363be088604ffa2ccba84ff7ad7250bc for pr-56481 Dec 05 04:48:19.136 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56481/worker-0/master#c8ae2de8363be088604ffa2ccba84ff7ad7250bc:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56481/master#c8ae2de8363be088604ffa2ccba84ff7ad7250bc:/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 +c8ae2de8363be088604ffa2ccba84ff7ad7250bc-alt check --frozen --all --all-targets" "-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"` Dec 05 04:48:19.438 INFO [stdout] 5d0c6b41049230b485b11e7e443a2e05549914e1a7f0b402b70b43a99d3cb775 Dec 05 04:48:19.444 INFO running `"docker" "start" "-a" "5d0c6b41049230b485b11e7e443a2e05549914e1a7f0b402b70b43a99d3cb775"` Dec 05 04:48:20.443 INFO [stderr] usermod: no changes Dec 05 04:48:20.502 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently Dec 05 04:48:20.502 INFO [stderr] disables Cargo from automatically inferring other binary targets. Dec 05 04:48:20.502 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following Dec 05 04:48:20.502 INFO [stderr] files will be included as a binary target: Dec 05 04:48:20.502 INFO [stderr] Dec 05 04:48:20.502 INFO [stderr] * /source/src/main.rs Dec 05 04:48:20.502 INFO [stderr] Dec 05 04:48:20.502 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be Dec 05 04:48:20.502 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself Dec 05 04:48:20.502 INFO [stderr] and disable this warning by adding `autobins = false` to your [package] Dec 05 04:48:20.502 INFO [stderr] section. You may also move the files to a location where Cargo would not Dec 05 04:48:20.502 INFO [stderr] automatically infer them to be a target, such as in subfolders. Dec 05 04:48:20.502 INFO [stderr] Dec 05 04:48:20.502 INFO [stderr] For more information on this warning you can consult Dec 05 04:48:20.502 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330 Dec 05 04:48:20.502 INFO [stderr] warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usirun`, Dec 05 04:48:20.502 INFO [stderr] please set bin.path in Cargo.toml Dec 05 04:48:20.502 INFO [stderr] warning: `panic` setting is ignored for `test` profile Dec 05 04:48:20.673 INFO [stderr] Checking itertools v0.6.5 Dec 05 04:48:20.678 INFO [stderr] Checking toml v0.3.2 Dec 05 04:48:20.679 INFO [stderr] Compiling bitintr v0.1.18 Dec 05 04:48:20.687 INFO [stderr] Checking nom v3.2.1 Dec 05 04:48:20.687 INFO [stderr] Checking indicatif v0.3.3 Dec 05 04:48:24.995 INFO [stderr] Checking csa v0.2.0 Dec 05 04:48:25.843 INFO [stderr] Checking shogi v0.7.0 Dec 05 04:48:25.843 INFO [stderr] Checking usi v0.1.0 Dec 05 04:48:29.107 INFO [stderr] Checking usi-run v0.5.0 (/source) Dec 05 04:48:34.080 INFO [stderr] warning: variable does not need to be mutable Dec 05 04:48:34.080 INFO [stderr] --> src/environment.rs:259:13 Dec 05 04:48:34.080 INFO [stderr] | Dec 05 04:48:34.080 INFO [stderr] 259 | let mut game = Game::new(tc.clone()); Dec 05 04:48:34.080 INFO [stderr] | ----^^^^ Dec 05 04:48:34.080 INFO [stderr] | | Dec 05 04:48:34.080 INFO [stderr] | help: remove this `mut` Dec 05 04:48:34.080 INFO [stderr] | Dec 05 04:48:34.080 INFO [stderr] = note: #[warn(unused_mut)] on by default Dec 05 04:48:34.080 INFO [stderr] Dec 05 04:48:34.219 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 13.75s Dec 05 04:48:34.227 INFO [stderr] su: No module specific data is present Dec 05 04:48:35.171 INFO running `"docker" "inspect" "5d0c6b41049230b485b11e7e443a2e05549914e1a7f0b402b70b43a99d3cb775"` Dec 05 04:48:35.553 INFO running `"docker" "rm" "-f" "5d0c6b41049230b485b11e7e443a2e05549914e1a7f0b402b70b43a99d3cb775"` Dec 05 04:48:35.899 INFO [stdout] 5d0c6b41049230b485b11e7e443a2e05549914e1a7f0b402b70b43a99d3cb775