Sep 14 11:36:01.790 INFO checking postscript-0.13.2 against try#87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0 for pr-53578-1
Sep 14 11:36:01.790 INFO running: cargo +87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0-alt check --frozen --all --all-targets
Sep 14 11:36:01.790 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53578-1/try#87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53578-1/worker-3/try#87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0:/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=1000" "-e" "CMD=cargo +87b8e7411c4f1267d0cac0d63fa9c21c943e2ea0-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"`
Sep 14 11:36:02.004 INFO blam! 59a2a99c6d7acdc759ccacb37e6b96e48ea0b14a4759c4dc62524f660ab50ff3
Sep 14 11:36:02.007 INFO running `"docker" "start" "-a" "59a2a99c6d7acdc759ccacb37e6b96e48ea0b14a4759c4dc62524f660ab50ff3"`
Sep 14 11:36:02.427 INFO kablam! usermod: no changes
Sep 14 11:36:02.448 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Sep 14 11:36:02.448 INFO kablam! disables Cargo from automatically inferring other test targets.
Sep 14 11:36:02.448 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 14 11:36:02.448 INFO kablam! files will be included as a test target:
Sep 14 11:36:02.448 INFO kablam! 
Sep 14 11:36:02.448 INFO kablam! * /source/tests/compact1.rs
Sep 14 11:36:02.448 INFO kablam! * /source/tests/type2.rs
Sep 14 11:36:02.448 INFO kablam! 
Sep 14 11:36:02.448 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 14 11:36:02.448 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Sep 14 11:36:02.448 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Sep 14 11:36:02.448 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 14 11:36:02.448 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 14 11:36:02.448 INFO kablam! 
Sep 14 11:36:02.448 INFO kablam! For more information on this warning you can consult
Sep 14 11:36:02.448 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 14 11:36:02.448 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Sep 14 11:36:02.448 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Sep 14 11:36:02.448 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 14 11:36:02.448 INFO kablam! files will be included as a benchmark target:
Sep 14 11:36:02.448 INFO kablam! 
Sep 14 11:36:02.448 INFO kablam! * /source/benches/compact1.rs
Sep 14 11:36:02.448 INFO kablam! * /source/benches/type2.rs
Sep 14 11:36:02.449 INFO kablam! 
Sep 14 11:36:02.449 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 14 11:36:02.449 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Sep 14 11:36:02.449 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Sep 14 11:36:02.449 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 14 11:36:02.449 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 14 11:36:02.449 INFO kablam! 
Sep 14 11:36:02.449 INFO kablam! For more information on this warning you can consult
Sep 14 11:36:02.449 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 14 11:36:02.453 INFO kablam!     Checking postscript v0.13.2 (file:///source)
Sep 14 11:36:03.850 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 1.41s
Sep 14 11:36:03.853 INFO kablam! su: No module specific data is present
Sep 14 11:36:04.465 INFO running `"docker" "rm" "-f" "59a2a99c6d7acdc759ccacb37e6b96e48ea0b14a4759c4dc62524f660ab50ff3"`
Sep 14 11:36:04.543 INFO blam! 59a2a99c6d7acdc759ccacb37e6b96e48ea0b14a4759c4dc62524f660ab50ff3