Sep 02 21:22:35.194 INFO checking acto-rs-0.5.2 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53851 Sep 02 21:22:35.194 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets Sep 02 21:22:35.194 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-1/pr-53851/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-1/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/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 +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 02 21:22:35.386 INFO blam! 1d2f4d70828f851f584e4262bb57d4d8efd4b9b67faf99488afa673b05ace7f2 Sep 02 21:22:35.389 INFO running `"docker" "start" "-a" "1d2f4d70828f851f584e4262bb57d4d8efd4b9b67faf99488afa673b05ace7f2"` Sep 02 21:22:36.061 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently Sep 02 21:22:36.061 INFO kablam! disables Cargo from automatically inferring other binary targets. Sep 02 21:22:36.061 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Sep 02 21:22:36.061 INFO kablam! files will be included as a binary target: Sep 02 21:22:36.061 INFO kablam! Sep 02 21:22:36.061 INFO kablam! * /source/src/main.rs Sep 02 21:22:36.061 INFO kablam! Sep 02 21:22:36.061 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Sep 02 21:22:36.061 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself Sep 02 21:22:36.062 INFO kablam! and disable this warning by adding `autobins = false` to your [package] Sep 02 21:22:36.062 INFO kablam! section. You may also move the files to a location where Cargo would not Sep 02 21:22:36.062 INFO kablam! automatically infer them to be a target, such as in subfolders. Sep 02 21:22:36.062 INFO kablam! Sep 02 21:22:36.062 INFO kablam! For more information on this warning you can consult Sep 02 21:22:36.062 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Sep 02 21:22:36.062 INFO kablam! warning: path `/source/src/main.rs` was erroneously implicitly accepted for binary `bench`, Sep 02 21:22:36.062 INFO kablam! please set bin.path in Cargo.toml Sep 02 21:22:36.071 INFO kablam! Checking lossyq v0.1.19 Sep 02 21:22:36.900 INFO kablam! Checking acto-rs v0.5.2 (file:///source) Sep 02 21:22:38.508 INFO kablam! warning: variable does not need to be mutable Sep 02 21:22:38.508 INFO kablam! --> src/scheduler/wrap.rs:19:11 Sep 02 21:22:38.509 INFO kablam! | Sep 02 21:22:38.509 INFO kablam! 19 | let mut slice = self.output_positions.as_mut_slice(); Sep 02 21:22:38.509 INFO kablam! | ----^^^^^ Sep 02 21:22:38.509 INFO kablam! | | Sep 02 21:22:38.509 INFO kablam! | help: remove this `mut` Sep 02 21:22:38.509 INFO kablam! | Sep 02 21:22:38.509 INFO kablam! = note: #[warn(unused_mut)] on by default Sep 02 21:22:38.509 INFO kablam! Sep 02 21:22:38.510 INFO kablam! warning: variable does not need to be mutable Sep 02 21:22:38.510 INFO kablam! --> src/scheduler/wrap.rs:35:9 Sep 02 21:22:38.510 INFO kablam! | Sep 02 21:22:38.510 INFO kablam! 35 | let mut slice = self.output_positions.as_mut_slice(); Sep 02 21:22:38.510 INFO kablam! | ----^^^^^ Sep 02 21:22:38.510 INFO kablam! | | Sep 02 21:22:38.510 INFO kablam! | help: remove this `mut` Sep 02 21:22:38.510 INFO kablam! Sep 02 21:22:38.514 INFO kablam! warning: variable does not need to be mutable Sep 02 21:22:38.514 INFO kablam! --> src/scheduler/page.rs:51:9 Sep 02 21:22:38.514 INFO kablam! | Sep 02 21:22:38.514 INFO kablam! 51 | let mut data_ref = &mut slice[idx]; Sep 02 21:22:38.514 INFO kablam! | ----^^^^^^^^ Sep 02 21:22:38.514 INFO kablam! | | Sep 02 21:22:38.514 INFO kablam! | help: remove this `mut` Sep 02 21:22:38.514 INFO kablam! Sep 02 21:22:38.654 INFO kablam! warning: variable does not need to be mutable Sep 02 21:22:38.654 INFO kablam! --> src/scheduler/wrap.rs:19:11 Sep 02 21:22:38.654 INFO kablam! | Sep 02 21:22:38.654 INFO kablam! 19 | let mut slice = self.output_positions.as_mut_slice(); Sep 02 21:22:38.654 INFO kablam! | ----^^^^^ Sep 02 21:22:38.654 INFO kablam! | | Sep 02 21:22:38.654 INFO kablam! | help: remove this `mut` Sep 02 21:22:38.654 INFO kablam! | Sep 02 21:22:38.655 INFO kablam! = note: #[warn(unused_mut)] on by default Sep 02 21:22:38.655 INFO kablam! Sep 02 21:22:38.655 INFO kablam! warning: variable does not need to be mutable Sep 02 21:22:38.655 INFO kablam! --> src/scheduler/wrap.rs:35:9 Sep 02 21:22:38.655 INFO kablam! | Sep 02 21:22:38.655 INFO kablam! 35 | let mut slice = self.output_positions.as_mut_slice(); Sep 02 21:22:38.655 INFO kablam! | ----^^^^^ Sep 02 21:22:38.655 INFO kablam! | | Sep 02 21:22:38.655 INFO kablam! | help: remove this `mut` Sep 02 21:22:38.655 INFO kablam! Sep 02 21:22:38.660 INFO kablam! warning: variable does not need to be mutable Sep 02 21:22:38.660 INFO kablam! --> src/scheduler/page.rs:51:9 Sep 02 21:22:38.660 INFO kablam! | Sep 02 21:22:38.660 INFO kablam! 51 | let mut data_ref = &mut slice[idx]; Sep 02 21:22:38.660 INFO kablam! | ----^^^^^^^^ Sep 02 21:22:38.660 INFO kablam! | | Sep 02 21:22:38.660 INFO kablam! | help: remove this `mut` Sep 02 21:22:38.660 INFO kablam! Sep 02 21:22:38.877 INFO kablam! warning: variable does not need to be mutable Sep 02 21:22:38.877 INFO kablam! --> src/bench/bitset.rs:19:9 Sep 02 21:22:38.877 INFO kablam! | Sep 02 21:22:38.877 INFO kablam! 19 | let mut slice = self.bits.as_mut_slice(); Sep 02 21:22:38.877 INFO kablam! | ----^^^^^ Sep 02 21:22:38.877 INFO kablam! | | Sep 02 21:22:38.877 INFO kablam! | help: remove this `mut` Sep 02 21:22:38.877 INFO kablam! Sep 02 21:22:39.549 INFO kablam! Finished dev [unoptimized + debuginfo] target(s) in 3.50s Sep 02 21:22:39.579 INFO kablam! su: No module specific data is present Sep 02 21:22:39.965 INFO running `"docker" "rm" "-f" "1d2f4d70828f851f584e4262bb57d4d8efd4b9b67faf99488afa673b05ace7f2"` Sep 02 21:22:40.057 INFO blam! 1d2f4d70828f851f584e4262bb57d4d8efd4b9b67faf99488afa673b05ace7f2