Jul 11 22:39:28.988 INFO checking sandbox-ipc-0.3.0 against master#ae5b629efd79de78e6ba7ef493c32857bd7f9cf9 for pr-52234
Jul 11 22:39:28.988 INFO running: cargo +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets
Jul 11 22:39:28.988 INFO creating container for: cargo +ae5b629efd79de78e6ba7ef493c32857bd7f9cf9-alt check --frozen --all --all-targets
Jul 11 22:39:28.988 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 22:39:29.254 INFO blam! 62d8a00d96318be29037610120a4c67fd4cb12589da44a41944e9694ec5506f0
Jul 11 22:39:29.256 INFO running `"docker" "start" "-a" "62d8a00d96318be29037610120a4c67fd4cb12589da44a41944e9694ec5506f0"`
Jul 11 22:39:30.175 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Jul 11 22:39:30.175 INFO kablam! disables Cargo from automatically inferring other test targets.
Jul 11 22:39:30.175 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Jul 11 22:39:30.176 INFO kablam! files will be included as a test target:
Jul 11 22:39:30.176 INFO kablam! 
Jul 11 22:39:30.176 INFO kablam! * /source/tests/mp_channel_base.rs
Jul 11 22:39:30.176 INFO kablam! 
Jul 11 22:39:30.176 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Jul 11 22:39:30.176 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Jul 11 22:39:30.176 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Jul 11 22:39:30.176 INFO kablam! section. You may also move the files to a location where Cargo would not
Jul 11 22:39:30.176 INFO kablam! automatically infer them to be a target, such as in subfolders.
Jul 11 22:39:30.176 INFO kablam! 
Jul 11 22:39:30.176 INFO kablam! For more information on this warning you can consult
Jul 11 22:39:30.176 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Jul 11 22:39:30.340 INFO kablam!    Compiling serde v1.0.70
Jul 11 22:39:56.263 INFO kablam!     Checking bincode v0.9.2
Jul 11 22:39:56.263 INFO kablam!     Checking uuid v0.5.1
Jul 11 22:39:56.263 INFO kablam!     Checking serde_json v1.0.22
Jul 11 22:39:59.443 INFO kablam!     Checking sandbox-ipc v0.3.0 (file:///source)
Jul 11 22:40:06.296 INFO kablam! warning: unused variable: `child`
Jul 11 22:40:06.296 INFO kablam!    --> src/unix/channel.rs:186:23
Jul 11 22:40:06.296 INFO kablam!     |
Jul 11 22:40:06.296 INFO kablam! 186 |     pub fn from_child(child: &process::Child) -> io::Result<Self> {
Jul 11 22:40:06.297 INFO kablam!     |                       ^^^^^ help: consider using `_child` instead
Jul 11 22:40:06.306 INFO kablam!     |
Jul 11 22:40:06.306 INFO kablam!     = note: #[warn(unused_variables)] on by default
Jul 11 22:40:06.306 INFO kablam! 
Jul 11 22:40:15.135 INFO kablam! warning: unused variable: `child`
Jul 11 22:40:15.135 INFO kablam!    --> src/unix/channel.rs:186:23
Jul 11 22:40:15.135 INFO kablam!     |
Jul 11 22:40:15.135 INFO kablam! 186 |     pub fn from_child(child: &process::Child) -> io::Result<Self> {
Jul 11 22:40:15.135 INFO kablam!     |                       ^^^^^ help: consider using `_child` instead
Jul 11 22:40:15.135 INFO kablam!     |
Jul 11 22:40:15.135 INFO kablam!     = note: #[warn(unused_variables)] on by default
Jul 11 22:40:15.135 INFO kablam! 
Jul 11 22:40:15.880 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 45.72s
Jul 11 22:40:15.914 INFO kablam! su: No module specific data is present
Jul 11 22:40:16.453 INFO running `"docker" "rm" "-f" "62d8a00d96318be29037610120a4c67fd4cb12589da44a41944e9694ec5506f0"`
Jul 11 22:40:16.614 INFO blam! 62d8a00d96318be29037610120a4c67fd4cb12589da44a41944e9694ec5506f0