Dec 04 16:15:21.452 INFO checking juli1/rust-json-example against try#1df97983eb2057dc6a8f7eb364e263b51ae23230 for pr-56481
Dec 04 16:15:21.452 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56481/worker-5/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-56481/try#1df97983eb2057dc6a8f7eb364e263b51ae23230:/source:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +1df97983eb2057dc6a8f7eb364e263b51ae23230-alt check --frozen --all --all-targets" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 04 16:15:21.992 INFO [stdout] 703c5354ba43861d22f631b973dbaa27a529b347e2ee277d440d0fccc9a007f2
Dec 04 16:15:22.003 INFO running `"docker" "start" "-a" "703c5354ba43861d22f631b973dbaa27a529b347e2ee277d440d0fccc9a007f2"`
Dec 04 16:15:23.102 INFO [stderr] usermod: no changes
Dec 04 16:15:23.160 INFO [stderr] warning: An explicit [[bin]] section is specified in Cargo.toml which currently
Dec 04 16:15:23.161 INFO [stderr] disables Cargo from automatically inferring other binary targets.
Dec 04 16:15:23.161 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 04 16:15:23.161 INFO [stderr] files will be included as a binary target:
Dec 04 16:15:23.161 INFO [stderr] 
Dec 04 16:15:23.161 INFO [stderr] * /source/src/main.rs
Dec 04 16:15:23.161 INFO [stderr] 
Dec 04 16:15:23.161 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 04 16:15:23.161 INFO [stderr] ready to be compiled as a binary target today. You can future-proof yourself
Dec 04 16:15:23.161 INFO [stderr] and disable this warning by adding `autobins = false` to your [package]
Dec 04 16:15:23.161 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 04 16:15:23.161 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 04 16:15:23.161 INFO [stderr] 
Dec 04 16:15:23.161 INFO [stderr] For more information on this warning you can consult
Dec 04 16:15:23.161 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 04 16:15:23.363 INFO [stderr]     Checking iovec v0.1.2
Dec 04 16:15:23.395 INFO [stderr]     Checking futures-cpupool v0.1.8
Dec 04 16:15:24.119 INFO [stderr]     Checking bytes v0.4.6
Dec 04 16:15:24.119 INFO [stderr]     Checking mio v0.6.12
Dec 04 16:15:26.371 INFO [stderr]     Checking tokio-io v0.1.4
Dec 04 16:15:26.371 INFO [stderr]     Checking http v0.1.4
Dec 04 16:15:29.245 INFO [stderr]     Checking tokio-core v0.1.12
Dec 04 16:15:32.048 INFO [stderr]     Checking tokio-proto v0.1.1
Dec 04 16:15:32.048 INFO [stderr]     Checking tokio-tls v0.1.4
Dec 04 16:15:35.459 INFO [stderr]     Checking hyper v0.11.16
Dec 04 16:15:40.811 INFO [stderr]     Checking hyper-tls v0.1.2
Dec 04 16:15:42.295 INFO [stderr]     Checking rust-json v0.1.0 (/source)
Dec 04 16:15:47.191 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 24.05s
Dec 04 16:15:47.216 INFO [stderr] su: No module specific data is present
Dec 04 16:15:47.793 INFO running `"docker" "inspect" "703c5354ba43861d22f631b973dbaa27a529b347e2ee277d440d0fccc9a007f2"`
Dec 04 16:15:48.036 INFO running `"docker" "rm" "-f" "703c5354ba43861d22f631b973dbaa27a529b347e2ee277d440d0fccc9a007f2"`
Dec 04 16:15:48.327 INFO [stdout] 703c5354ba43861d22f631b973dbaa27a529b347e2ee277d440d0fccc9a007f2