Sep 03 18:09:19.520 INFO checking juli1/rust-json-example against try#6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0 for pr-53893 Sep 03 18:09:19.520 INFO running: cargo +6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0-alt check --frozen --all --all-targets Sep 03 18:09:19.520 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53893/try#6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53893/worker-3/try#6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0:/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 +6b43b862fabb13a0ce2a5371ea1e77ee1674b7e0-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 03 18:09:19.783 INFO blam! 0890d6052389b86196027435634d3bb7f2f7f98d12c1f9479f38155ba5bf6de1 Sep 03 18:09:19.785 INFO running `"docker" "start" "-a" "0890d6052389b86196027435634d3bb7f2f7f98d12c1f9479f38155ba5bf6de1"` Sep 03 18:09:20.692 INFO kablam! warning: An explicit [[bin]] section is specified in Cargo.toml which currently Sep 03 18:09:20.692 INFO kablam! disables Cargo from automatically inferring other binary targets. Sep 03 18:09:20.692 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Sep 03 18:09:20.692 INFO kablam! files will be included as a binary target: Sep 03 18:09:20.692 INFO kablam! Sep 03 18:09:20.692 INFO kablam! * /source/src/main.rs Sep 03 18:09:20.692 INFO kablam! Sep 03 18:09:20.692 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Sep 03 18:09:20.692 INFO kablam! ready to be compiled as a binary target today. You can future-proof yourself Sep 03 18:09:20.692 INFO kablam! and disable this warning by adding `autobins = false` to your [package] Sep 03 18:09:20.692 INFO kablam! section. You may also move the files to a location where Cargo would not Sep 03 18:09:20.692 INFO kablam! automatically infer them to be a target, such as in subfolders. Sep 03 18:09:20.692 INFO kablam! Sep 03 18:09:20.693 INFO kablam! For more information on this warning you can consult Sep 03 18:09:20.693 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Sep 03 18:09:21.001 INFO kablam! Checking tokio v0.0.0 Sep 03 18:09:21.001 INFO kablam! Checking rand v0.3.20 Sep 03 18:09:21.011 INFO kablam! Checking http v0.1.4 Sep 03 18:09:21.014 INFO kablam! Checking tokio-io v0.1.4 Sep 03 18:09:21.017 INFO kablam! Checking mio v0.6.12 Sep 03 18:09:26.491 INFO kablam! Checking tokio-core v0.1.12 Sep 03 18:09:29.407 INFO kablam! Checking tokio-proto v0.1.1 Sep 03 18:09:29.408 INFO kablam! Checking tokio-tls v0.1.4 Sep 03 18:09:34.347 INFO kablam! Checking hyper v0.11.16 Sep 03 18:09:43.954 INFO kablam! Checking hyper-tls v0.1.2 Sep 03 18:09:44.779 INFO kablam! Checking rust-json v0.1.0 (file:///source) Sep 03 18:09:46.147 INFO kablam! Finished dev [unoptimized + debuginfo] target(s) in 25.49s Sep 03 18:09:46.161 INFO kablam! su: No module specific data is present Sep 03 18:09:46.571 INFO running `"docker" "rm" "-f" "0890d6052389b86196027435634d3bb7f2f7f98d12c1f9479f38155ba5bf6de1"` Sep 03 18:09:46.677 INFO blam! 0890d6052389b86196027435634d3bb7f2f7f98d12c1f9479f38155ba5bf6de1