Sep 14 11:36:06.112 INFO checking postscript-0.11.1 against master#90d36fb5905bbe5004f5b465ea14b53d10dae260 for pr-53578-1 Sep 14 11:36:06.112 INFO running: cargo +90d36fb5905bbe5004f5b465ea14b53d10dae260-alt check --frozen --all --all-targets Sep 14 11:36:06.112 INFO running `"docker" "create" "-v" "/home/ec2-user/crater/./work/local/test-source/worker-6/pr-53578-1/master#90d36fb5905bbe5004f5b465ea14b53d10dae260:/source:ro,Z" "-v" "/home/ec2-user/crater/./work/local/target-dirs/pr-53578-1/worker-6/master#90d36fb5905bbe5004f5b465ea14b53d10dae260:/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 +90d36fb5905bbe5004f5b465ea14b53d10dae260-alt check --frozen --all --all-targets" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-m" "2G" "crater"` Sep 14 11:36:06.250 INFO blam! 75c1acf64c5f5410b7671fe236b3ff158a2be6994f0f1fb713b926e3ff1ae19b Sep 14 11:36:06.252 INFO running `"docker" "start" "-a" "75c1acf64c5f5410b7671fe236b3ff158a2be6994f0f1fb713b926e3ff1ae19b"` Sep 14 11:36:07.267 INFO kablam! usermod: no changes Sep 14 11:36:07.286 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently Sep 14 11:36:07.286 INFO kablam! disables Cargo from automatically inferring other test targets. Sep 14 11:36:07.286 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Sep 14 11:36:07.286 INFO kablam! files will be included as a test target: Sep 14 11:36:07.286 INFO kablam! Sep 14 11:36:07.286 INFO kablam! * /source/tests/compact.rs Sep 14 11:36:07.286 INFO kablam! * /source/tests/type2.rs Sep 14 11:36:07.286 INFO kablam! Sep 14 11:36:07.286 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Sep 14 11:36:07.286 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself Sep 14 11:36:07.286 INFO kablam! and disable this warning by adding `autotests = false` to your [package] Sep 14 11:36:07.286 INFO kablam! section. You may also move the files to a location where Cargo would not Sep 14 11:36:07.286 INFO kablam! automatically infer them to be a target, such as in subfolders. Sep 14 11:36:07.286 INFO kablam! Sep 14 11:36:07.286 INFO kablam! For more information on this warning you can consult Sep 14 11:36:07.286 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Sep 14 11:36:07.286 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently Sep 14 11:36:07.286 INFO kablam! disables Cargo from automatically inferring other benchmark targets. Sep 14 11:36:07.286 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following Sep 14 11:36:07.286 INFO kablam! files will be included as a benchmark target: Sep 14 11:36:07.286 INFO kablam! Sep 14 11:36:07.286 INFO kablam! * /source/benches/compact.rs Sep 14 11:36:07.286 INFO kablam! * /source/benches/type2.rs Sep 14 11:36:07.286 INFO kablam! Sep 14 11:36:07.286 INFO kablam! This is likely to break cargo build or cargo test as these files may not be Sep 14 11:36:07.286 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself Sep 14 11:36:07.286 INFO kablam! and disable this warning by adding `autobenches = false` to your [package] Sep 14 11:36:07.286 INFO kablam! section. You may also move the files to a location where Cargo would not Sep 14 11:36:07.286 INFO kablam! automatically infer them to be a target, such as in subfolders. Sep 14 11:36:07.286 INFO kablam! Sep 14 11:36:07.286 INFO kablam! For more information on this warning you can consult Sep 14 11:36:07.286 INFO kablam! https://github.com/rust-lang/cargo/issues/5330 Sep 14 11:36:07.289 INFO kablam! Checking postscript v0.11.1 (file:///source) Sep 14 11:36:07.289 INFO kablam! Checking random v0.12.2 Sep 14 11:36:09.425 INFO kablam! Finished dev [unoptimized + debuginfo] target(s) in 2.14s Sep 14 11:36:09.426 INFO kablam! su: No module specific data is present Sep 14 11:36:10.432 INFO running `"docker" "rm" "-f" "75c1acf64c5f5410b7671fe236b3ff158a2be6994f0f1fb713b926e3ff1ae19b"` Sep 14 11:36:10.691 INFO blam! 75c1acf64c5f5410b7671fe236b3ff158a2be6994f0f1fb713b926e3ff1ae19b