Jul 11 18:27:00.470 INFO checking usi-run-0.5.0 against master#ae5b629efd79de78e6ba7ef493c32857bd7f9cf9 for pr-52234
Jul 11 18:27:00.470 INFO running: cargo +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets
Jul 11 18:27:00.470 INFO creating container for: cargo +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets
Jul 11 18:27:00.470 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-1/pr-52234/master#ae5b629efd79de78e6ba7ef493c32857bd7f9cf9:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-52234/worker-1/master#ae5b629efd79de78e6ba7ef493c32857bd7f9cf9:/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=500" "-e" "CMD=cargo +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "crater"`
Jul 11 18:27:00.736 INFO blam! b5f0a613e53802f23d7aa1ef3e8307f737fbe8db65355957480025e2cf949c93
Jul 11 18:27:00.737 INFO running `"docker" "start" "-a" "b5f0a613e53802f23d7aa1ef3e8307f737fbe8db65355957480025e2cf949c93"`
Jul 11 18:27:01.847 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Jul 11 18:27:01.847 INFO kablam! disables Cargo from automatically inferring other binary targets.
Jul 11 18:27:01.847 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Jul 11 18:27:01.848 INFO kablam! files will be included as a binary target:
Jul 11 18:27:01.848 INFO kablam! 
Jul 11 18:27:01.848 INFO kablam! * /source/src/main.rs
Jul 11 18:27:01.848 INFO kablam! 
Jul 11 18:27:01.848 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Jul 11 18:27:01.848 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Jul 11 18:27:01.848 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Jul 11 18:27:01.848 INFO kablam! section. You may also move the files to a location where Cargo would not
Jul 11 18:27:01.848 INFO kablam! automatically infer them to be a target, such as in subfolders.
Jul 11 18:27:01.848 INFO kablam! 
Jul 11 18:27:01.848 INFO kablam! For more information on this warning you can consult
Jul 11 18:27:01.848 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Jul 11 18:27:01.848 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `usirun`,
Jul 11 18:27:01.848 INFO kablam! please set bin.path in Cargo.toml
Jul 11 18:27:01.848 INFO kablam! warning: `panic` setting is ignored for `test` profile
Jul 11 18:27:02.009 INFO kablam!     Checking itertools v0.6.5
Jul 11 18:27:02.011 INFO kablam!     Checking toml v0.3.2
Jul 11 18:27:02.011 INFO kablam!    Compiling bitintr v0.1.18
Jul 11 18:27:02.015 INFO kablam!     Checking indicatif v0.3.3
Jul 11 18:27:02.016 INFO kablam!     Checking csa v0.2.0
Jul 11 18:27:12.200 INFO kablam!     Checking usi v0.1.0
Jul 11 18:27:12.202 INFO kablam!     Checking shogi v0.7.0
Jul 11 18:27:16.395 INFO kablam!     Checking usi-run v0.5.0 (file:///source)
Jul 11 18:27:18.951 INFO kablam! warning: variable does not need to be mutable
Jul 11 18:27:18.951 INFO kablam!    --> src/environment.rs:259:13
Jul 11 18:27:18.951 INFO kablam!     |
Jul 11 18:27:18.951 INFO kablam! 259 |         let mut game = Game::new(tc.clone());
Jul 11 18:27:18.951 INFO kablam!     |             ----^^^^
Jul 11 18:27:18.951 INFO kablam!     |             |
Jul 11 18:27:18.951 INFO kablam!     |             help: remove this `mut`
Jul 11 18:27:18.951 INFO kablam!     |
Jul 11 18:27:18.951 INFO kablam!     = note: #[warn(unused_mut)] on by default
Jul 11 18:27:18.951 INFO kablam! 
Jul 11 18:27:19.296 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 17.49s
Jul 11 18:27:19.315 INFO kablam! su: No module specific data is present
Jul 11 18:27:19.854 INFO running `"docker" "rm" "-f" "b5f0a613e53802f23d7aa1ef3e8307f737fbe8db65355957480025e2cf949c93"`
Jul 11 18:27:20.006 INFO blam! b5f0a613e53802f23d7aa1ef3e8307f737fbe8db65355957480025e2cf949c93