Sep 14 07:03:42.419 INFO checking usi-run-0.5.0 against try#87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0 for pr-53578-1
Sep 14 07:03:42.419 INFO running: cargo +87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0-alt check --frozen --all --all-targets
Sep 14 07:03:42.419 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-6/pr-53578-1/try#87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53578-1/worker-6/try#87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0:/target:rw,Z" "-v" "/home/ec2-user/crater/./work/local/cargo-home:/cargo-home:ro,Z" "-v" "/home/ec2-user/crater/./work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "CMD=cargo +87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"`
Sep 14 07:03:42.570 INFO blam! 3c5343a46f2411033fb8d916f8cbb32e923787edb0e3ae5a68450ec700904b6a
Sep 14 07:03:42.571 INFO running `"docker" "start" "-a" "3c5343a46f2411033fb8d916f8cbb32e923787edb0e3ae5a68450ec700904b6a"`
Sep 14 07:03:43.890 INFO kablam! usermod: no changes
Sep 14 07:03:43.910 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Sep 14 07:03:43.910 INFO kablam! disables Cargo from automatically inferring other binary targets.
Sep 14 07:03:43.910 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 14 07:03:43.910 INFO kablam! files will be included as a binary target:
Sep 14 07:03:43.910 INFO kablam! 
Sep 14 07:03:43.910 INFO kablam! * /source/src/main.rs
Sep 14 07:03:43.910 INFO kablam! 
Sep 14 07:03:43.910 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 14 07:03:43.910 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Sep 14 07:03:43.910 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Sep 14 07:03:43.910 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 14 07:03:43.910 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 14 07:03:43.910 INFO kablam! 
Sep 14 07:03:43.910 INFO kablam! For more information on this warning you can consult
Sep 14 07:03:43.910 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 14 07:03:43.910 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usirun`,
Sep 14 07:03:43.910 INFO kablam! please set bin.path in Cargo.toml
Sep 14 07:03:43.910 INFO kablam! warning: `panic` setting is ignored for `test` profile
Sep 14 07:03:44.031 INFO kablam!     Checking clicolors-control v0.2.0
Sep 14 07:03:44.031 INFO kablam!     Checking itertools v0.6.5
Sep 14 07:03:44.031 INFO kablam!     Checking toml v0.3.2
Sep 14 07:03:44.032 INFO kablam!    Compiling bitintr v0.1.18
Sep 14 07:03:44.033 INFO kablam!     Checking csa v0.2.0
Sep 14 07:03:44.415 INFO kablam!     Checking indicatif v0.3.3
Sep 14 07:03:47.060 INFO kablam!     Checking usi v0.1.0
Sep 14 07:03:47.060 INFO kablam!     Checking shogi v0.7.0
Sep 14 07:03:48.993 INFO kablam!     Checking usi-run v0.5.0 (file:///source)
Sep 14 07:03:50.126 INFO kablam! warning: variable does not need to be mutable
Sep 14 07:03:50.127 INFO kablam!    --> src/environment.rs:259:13
Sep 14 07:03:50.127 INFO kablam!     |
Sep 14 07:03:50.127 INFO kablam! 259 |         let mut game = Game::new(tc.clone());
Sep 14 07:03:50.127 INFO kablam!     |             ----^^^^
Sep 14 07:03:50.127 INFO kablam!     |             |
Sep 14 07:03:50.127 INFO kablam!     |             help: remove this `mut`
Sep 14 07:03:50.127 INFO kablam!     |
Sep 14 07:03:50.127 INFO kablam!     = note: #[warn(unused_mut)] on by default
Sep 14 07:03:50.127 INFO kablam! 
Sep 14 07:03:50.442 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 6.52s
Sep 14 07:03:50.443 INFO kablam! su: No module specific data is present
Sep 14 07:03:51.304 INFO running `"docker" "rm" "-f" "3c5343a46f2411033fb8d916f8cbb32e923787edb0e3ae5a68450ec700904b6a"`
Sep 14 07:03:51.383 INFO blam! 3c5343a46f2411033fb8d916f8cbb32e923787edb0e3ae5a68450ec700904b6a