Sep 17 19:48:01.568 INFO checking postscript-0.11.1 against master#cb6d2dfa8923902b0992a1522dc4a45a9d3ba690 for pr-54033
Sep 17 19:48:01.568 INFO running: cargo +cb6d2dfa8923902b0992a1522dc4a45a9d3ba690-alt check --frozen --all --all-targets
Sep 17 19:48:01.568 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-2/pr-54033/master#cb6d2dfa8923902b0992a1522dc4a45a9d3ba690:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-54033/worker-2/master#cb6d2dfa8923902b0992a1522dc4a45a9d3ba690:/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 +cb6d2dfa8923902b0992a1522dc4a45a9d3ba690-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "1536M" "crater"`
Sep 17 19:48:01.774 INFO blam! 871b2fdc5f3aad03115f499c844955a5fdf3359a6dc2f4fea4794b0ea663d7ba
Sep 17 19:48:01.776 INFO running `"docker" "start" "-a" "871b2fdc5f3aad03115f499c844955a5fdf3359a6dc2f4fea4794b0ea663d7ba"`
Sep 17 19:48:02.603 INFO kablam! usermod: no changes
Sep 17 19:48:02.623 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Sep 17 19:48:02.623 INFO kablam! disables Cargo from automatically inferring other test targets.
Sep 17 19:48:02.623 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 17 19:48:02.623 INFO kablam! files will be included as a test target:
Sep 17 19:48:02.623 INFO kablam! 
Sep 17 19:48:02.623 INFO kablam! * /source/tests/compact.rs
Sep 17 19:48:02.623 INFO kablam! * /source/tests/type2.rs
Sep 17 19:48:02.623 INFO kablam! 
Sep 17 19:48:02.623 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 17 19:48:02.623 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Sep 17 19:48:02.623 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Sep 17 19:48:02.623 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 17 19:48:02.623 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 17 19:48:02.623 INFO kablam! 
Sep 17 19:48:02.623 INFO kablam! For more information on this warning you can consult
Sep 17 19:48:02.623 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 17 19:48:02.623 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Sep 17 19:48:02.623 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Sep 17 19:48:02.623 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 17 19:48:02.623 INFO kablam! files will be included as a benchmark target:
Sep 17 19:48:02.623 INFO kablam! 
Sep 17 19:48:02.623 INFO kablam! * /source/benches/compact.rs
Sep 17 19:48:02.623 INFO kablam! * /source/benches/type2.rs
Sep 17 19:48:02.623 INFO kablam! 
Sep 17 19:48:02.623 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 17 19:48:02.623 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Sep 17 19:48:02.623 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Sep 17 19:48:02.623 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 17 19:48:02.623 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 17 19:48:02.623 INFO kablam! 
Sep 17 19:48:02.623 INFO kablam! For more information on this warning you can consult
Sep 17 19:48:02.623 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 17 19:48:02.628 INFO kablam!     Checking postscript v0.11.1 (/source)
Sep 17 19:48:04.911 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.30s
Sep 17 19:48:04.915 INFO kablam! su: No module specific data is present
Sep 17 19:48:06.198 INFO running `"docker" "rm" "-f" "871b2fdc5f3aad03115f499c844955a5fdf3359a6dc2f4fea4794b0ea663d7ba"`
Sep 17 19:48:06.543 INFO blam! 871b2fdc5f3aad03115f499c844955a5fdf3359a6dc2f4fea4794b0ea663d7ba