Sep 01 15:00:03.936 INFO checking juli1/rust-json-example against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53851
Sep 01 15:00:03.936 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets
Sep 01 15:00:03.936 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53851/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53851/worker-3/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 01 15:00:04.150 INFO blam! 0f9323add620fbd4d9107aba179a1780df4a18247b597d6b137b8bca62a0c764
Sep 01 15:00:04.152 INFO running `"docker" "start" "-a" "0f9323add620fbd4d9107aba179a1780df4a18247b597d6b137b8bca62a0c764"`
Sep 01 15:00:04.961 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Sep 01 15:00:04.961 INFO kablam! disables Cargo from automatically inferring other binary targets.
Sep 01 15:00:04.961 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 01 15:00:04.961 INFO kablam! files will be included as a binary target:
Sep 01 15:00:04.961 INFO kablam! 
Sep 01 15:00:04.961 INFO kablam! * /source/src/main.rs
Sep 01 15:00:04.961 INFO kablam! 
Sep 01 15:00:04.961 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 01 15:00:04.961 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself
Sep 01 15:00:04.961 INFO kablam! and disable this warning by adding `autobins = false` to your [package]
Sep 01 15:00:04.961 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 01 15:00:04.961 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 01 15:00:04.961 INFO kablam! 
Sep 01 15:00:04.961 INFO kablam! For more information on this warning you can consult
Sep 01 15:00:04.962 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 01 15:00:05.150 INFO kablam!     Checking tokio v0.0.0
Sep 01 15:00:05.157 INFO kablam!     Checking tokio-service v0.1.0
Sep 01 15:00:05.161 INFO kablam!     Checking relay v0.1.1
Sep 01 15:00:05.166 INFO kablam!     Checking futures-cpupool v0.1.8
Sep 01 15:00:05.170 INFO kablam!     Checking tokio-io v0.1.4
Sep 01 15:00:05.173 INFO kablam!     Checking http v0.1.4
Sep 01 15:00:05.177 INFO kablam!     Checking native-tls v0.1.5
Sep 01 15:00:07.631 INFO kablam!     Checking tokio-core v0.1.12
Sep 01 15:00:09.935 INFO kablam!     Checking tokio-proto v0.1.1
Sep 01 15:00:09.935 INFO kablam!     Checking tokio-tls v0.1.4
Sep 01 15:00:13.833 INFO kablam!     Checking hyper v0.11.16
Sep 01 15:00:23.215 INFO kablam!     Checking hyper-tls v0.1.2
Sep 01 15:00:24.274 INFO kablam!     Checking rust-json v0.1.0 (file:///source)
Sep 01 15:00:26.222 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 21.27s
Sep 01 15:00:26.237 INFO kablam! su: No module specific data is present
Sep 01 15:00:26.655 INFO running `"docker" "rm" "-f" "0f9323add620fbd4d9107aba179a1780df4a18247b597d6b137b8bca62a0c764"`
Sep 01 15:00:26.823 INFO blam! 0f9323add620fbd4d9107aba179a1780df4a18247b597d6b137b8bca62a0c764