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