Oct 13 10:43:16.206 INFO checking postscript-0.13.2 against master#5af0bb83044c3fb43d59ad5f49ee5ae1a293901f for pr-54977
Oct 13 10:43:16.206 INFO running `"docker" "create" "-v" "/mnt/big/crater/./work/local/target-dirs/pr-54977/worker-0/master#5af0bb83044c3fb43d59ad5f49ee5ae1a293901f:/target:rw,Z" "-v" "/mnt/big/crater/./work/local/test-source/worker-0/pr-54977/master#5af0bb83044c3fb43d59ad5f49ee5ae1a293901f:/source:ro,Z" "-v" "/mnt/big/crater/./work/local/cargo-home:/cargo-home:ro,Z" "-v" "/mnt/big/crater/./work/local/rustup-home:/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/source" "-e" "USER_ID=1000" "-e" "CMD=cargo +5af0bb83044c3fb43d59ad5f49ee5ae1a293901f-alt check --frozen --all --all-targets" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Oct 13 10:43:16.496 INFO blam! fe73e42fd49bbe43770e51393b52a5762d0f49d4d9543819fd647a9b54a087a3
Oct 13 10:43:16.505 INFO running `"docker" "start" "-a" "fe73e42fd49bbe43770e51393b52a5762d0f49d4d9543819fd647a9b54a087a3"`
Oct 13 10:43:17.200 INFO kablam! usermod: no changes
Oct 13 10:43:17.222 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Oct 13 10:43:17.223 INFO kablam! disables Cargo from automatically inferring other test targets.
Oct 13 10:43:17.223 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Oct 13 10:43:17.223 INFO kablam! files will be included as a test target:
Oct 13 10:43:17.223 INFO kablam! 
Oct 13 10:43:17.223 INFO kablam! * /source/tests/compact1.rs
Oct 13 10:43:17.223 INFO kablam! * /source/tests/type2.rs
Oct 13 10:43:17.223 INFO kablam! 
Oct 13 10:43:17.223 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Oct 13 10:43:17.223 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Oct 13 10:43:17.223 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Oct 13 10:43:17.223 INFO kablam! section. You may also move the files to a location where Cargo would not
Oct 13 10:43:17.223 INFO kablam! automatically infer them to be a target, such as in subfolders.
Oct 13 10:43:17.223 INFO kablam! 
Oct 13 10:43:17.223 INFO kablam! For more information on this warning you can consult
Oct 13 10:43:17.223 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Oct 13 10:43:17.223 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Oct 13 10:43:17.223 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Oct 13 10:43:17.223 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Oct 13 10:43:17.223 INFO kablam! files will be included as a benchmark target:
Oct 13 10:43:17.223 INFO kablam! 
Oct 13 10:43:17.223 INFO kablam! * /source/benches/compact1.rs
Oct 13 10:43:17.223 INFO kablam! * /source/benches/type2.rs
Oct 13 10:43:17.223 INFO kablam! 
Oct 13 10:43:17.223 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Oct 13 10:43:17.223 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Oct 13 10:43:17.223 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Oct 13 10:43:17.223 INFO kablam! section. You may also move the files to a location where Cargo would not
Oct 13 10:43:17.223 INFO kablam! automatically infer them to be a target, such as in subfolders.
Oct 13 10:43:17.223 INFO kablam! 
Oct 13 10:43:17.223 INFO kablam! For more information on this warning you can consult
Oct 13 10:43:17.223 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Oct 13 10:43:17.227 INFO kablam!     Checking postscript v0.13.2 (/source)
Oct 13 10:43:20.202 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.98s
Oct 13 10:43:20.208 INFO kablam! su: No module specific data is present
Oct 13 10:43:20.894 INFO running `"docker" "rm" "-f" "fe73e42fd49bbe43770e51393b52a5762d0f49d4d9543819fd647a9b54a087a3"`
Oct 13 10:43:21.164 INFO blam! fe73e42fd49bbe43770e51393b52a5762d0f49d4d9543819fd647a9b54a087a3