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