Sep 01 11:01:04.071 INFO checking postscript-0.13.2 against master#1114ab684fbad001c4e580326d8eb4d8c4e917d3 for pr-53831
Sep 01 11:01:04.071 INFO running: cargo +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets
Sep 01 11:01:04.071 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-3/pr-53831/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53831/worker-3/master#1114ab684fbad001c4e580326d8eb4d8c4e917d3:/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 +1114ab684fbad001c4e580326d8eb4d8c4e917d3-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"`
Sep 01 11:01:04.259 INFO blam! bb7730f04ac0fb71e2c9f5d1d641cdf405e6066a44546a9dca4ace6790524625
Sep 01 11:01:04.262 INFO running `"docker" "start" "-a" "bb7730f04ac0fb71e2c9f5d1d641cdf405e6066a44546a9dca4ace6790524625"`
Sep 01 11:01:04.883 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Sep 01 11:01:04.884 INFO kablam! disables Cargo from automatically inferring other test targets.
Sep 01 11:01:04.884 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 01 11:01:04.884 INFO kablam! files will be included as a test target:
Sep 01 11:01:04.884 INFO kablam! 
Sep 01 11:01:04.884 INFO kablam! * /source/tests/type2.rs
Sep 01 11:01:04.884 INFO kablam! * /source/tests/compact1.rs
Sep 01 11:01:04.884 INFO kablam! 
Sep 01 11:01:04.884 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 01 11:01:04.884 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Sep 01 11:01:04.884 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Sep 01 11:01:04.884 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 01 11:01:04.884 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 01 11:01:04.884 INFO kablam! 
Sep 01 11:01:04.884 INFO kablam! For more information on this warning you can consult
Sep 01 11:01:04.884 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 01 11:01:04.884 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Sep 01 11:01:04.884 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Sep 01 11:01:04.884 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Sep 01 11:01:04.884 INFO kablam! files will be included as a benchmark target:
Sep 01 11:01:04.884 INFO kablam! 
Sep 01 11:01:04.884 INFO kablam! * /source/benches/type2.rs
Sep 01 11:01:04.884 INFO kablam! * /source/benches/compact1.rs
Sep 01 11:01:04.884 INFO kablam! 
Sep 01 11:01:04.884 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Sep 01 11:01:04.885 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Sep 01 11:01:04.885 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Sep 01 11:01:04.885 INFO kablam! section. You may also move the files to a location where Cargo would not
Sep 01 11:01:04.885 INFO kablam! automatically infer them to be a target, such as in subfolders.
Sep 01 11:01:04.885 INFO kablam! 
Sep 01 11:01:04.885 INFO kablam! For more information on this warning you can consult
Sep 01 11:01:04.885 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Sep 01 11:01:04.892 INFO kablam!     Checking postscript v0.13.2 (file:///source)
Sep 01 11:01:04.893 INFO kablam!     Checking random v0.12.2
Sep 01 11:01:07.852 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.97s
Sep 01 11:01:07.855 INFO kablam! su: No module specific data is present
Sep 01 11:01:08.342 INFO running `"docker" "rm" "-f" "bb7730f04ac0fb71e2c9f5d1d641cdf405e6066a44546a9dca4ace6790524625"`
Sep 01 11:01:08.439 INFO blam! bb7730f04ac0fb71e2c9f5d1d641cdf405e6066a44546a9dca4ace6790524625