Sep 02 00:51:50.098 INFO checking sandbox-ipc-0.3.0 against try#952c7dbfa2628309f557b367929ffc17af20b332 for pr-53851
Sep 02 00:51:50.098 INFO running: cargo +952c7dbfa2628309f557b367929ffc17af20b332-alt check --frozen --all --all-targets
Sep 02 00:51:50.098 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-1/pr-53851/try#952c7dbfa2628309f557b367929ffc17af20b332:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-1/try#952c7dbfa2628309f557b367929ffc17af20b332:/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 +952c7dbfa2628309f557b367929ffc17af20b332-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"`
Sep 02 00:51:50.337 INFO blam! b81d16fda96e98c7da7beacc5672f4894ea899891d5222f9b38d67b6d40d91cf
Sep 02 00:51:50.339 INFO running `"docker" "start" "-a" "b81d16fda96e98c7da7beacc5672f4894ea899891d5222f9b38d67b6d40d91cf"`
Sep 02 00:51:50.951 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Sep 02 00:51:50.951 INFO kablam! disables Cargo from automatically inferring other test targets.
Sep 02 00:51:50.951 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 02 00:51:50.951 INFO kablam! files will be included as a test target:
Sep 02 00:51:50.951 INFO kablam! 
Sep 02 00:51:50.951 INFO kablam! * /source/tests/mp_channel_base.rs
Sep 02 00:51:50.951 INFO kablam! 
Sep 02 00:51:50.951 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 02 00:51:50.951 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Sep 02 00:51:50.951 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Sep 02 00:51:50.951 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 02 00:51:50.951 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 02 00:51:50.951 INFO kablam! 
Sep 02 00:51:50.951 INFO kablam! For more information on this warning you can consult
Sep 02 00:51:50.952 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 02 00:51:51.058 INFO kablam!     Checking bincode v0.9.2
Sep 02 00:51:51.058 INFO kablam!     Checking uuid v0.5.1
Sep 02 00:51:52.243 INFO kablam!     Checking sandbox-ipc v0.3.0 (file:///source)
Sep 02 00:51:55.850 INFO kablam! warning: unused variable: `child`
Sep 02 00:51:55.850 INFO kablam!    --> src/unix/channel.rs:186:23
Sep 02 00:51:55.850 INFO kablam!     |
Sep 02 00:51:55.850 INFO kablam! 186 |     pub fn from_child(child: &process::Child) -> io::Result<Self> {
Sep 02 00:51:55.850 INFO kablam!     |                       ^^^^^ help: consider using `_child` instead
Sep 02 00:51:55.850 INFO kablam!     |
Sep 02 00:51:55.851 INFO kablam!     = note: #[warn(unused_variables)] on by default
Sep 02 00:51:55.851 INFO kablam! 
Sep 02 00:51:55.977 INFO kablam! warning: unused variable: `child`
Sep 02 00:51:55.977 INFO kablam!    --> src/unix/channel.rs:186:23
Sep 02 00:51:55.977 INFO kablam!     |
Sep 02 00:51:55.978 INFO kablam! 186 |     pub fn from_child(child: &process::Child) -> io::Result<Self> {
Sep 02 00:51:55.978 INFO kablam!     |                       ^^^^^ help: consider using `_child` instead
Sep 02 00:51:55.978 INFO kablam!     |
Sep 02 00:51:55.978 INFO kablam!     = note: #[warn(unused_variables)] on by default
Sep 02 00:51:55.978 INFO kablam! 
Sep 02 00:52:00.614 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 9.67s
Sep 02 00:52:00.624 INFO kablam! su: No module specific data is present
Sep 02 00:52:01.161 INFO running `"docker" "rm" "-f" "b81d16fda96e98c7da7beacc5672f4894ea899891d5222f9b38d67b6d40d91cf"`
Sep 02 00:52:01.309 INFO blam! b81d16fda96e98c7da7beacc5672f4894ea899891d5222f9b38d67b6d40d91cf