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