Nov 01 18:26:08.111 INFO checking postscript-0.13.2 against try#d7816399d50d407bbce1efe9dbadf8faaaf568fc for pr-55538
Nov 01 18:26:08.111 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55538/worker-4/try#d7816399d50d407bbce1efe9dbadf8faaaf568fc:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55538/try#d7816399d50d407bbce1efe9dbadf8faaaf568fc:/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 +d7816399d50d407bbce1efe9dbadf8faaaf568fc-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"`
Nov 01 18:26:08.539 INFO blam! 05158c4b7df542c0c969a0d37628928d3f7cdc98c7da203535d2ed2d4c22117f
Nov 01 18:26:08.548 INFO running `"docker" "start" "-a" "05158c4b7df542c0c969a0d37628928d3f7cdc98c7da203535d2ed2d4c22117f"`
Nov 01 18:26:09.289 INFO kablam! usermod: no changes
Nov 01 18:26:09.357 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 01 18:26:09.357 INFO kablam! disables Cargo from automatically inferring other test targets.
Nov 01 18:26:09.358 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 18:26:09.359 INFO kablam! files will be included as a test target:
Nov 01 18:26:09.359 INFO kablam! 
Nov 01 18:26:09.359 INFO kablam! * /source/tests/compact1.rs
Nov 01 18:26:09.359 INFO kablam! * /source/tests/type2.rs
Nov 01 18:26:09.360 INFO kablam! 
Nov 01 18:26:09.360 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 18:26:09.360 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Nov 01 18:26:09.361 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Nov 01 18:26:09.361 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 18:26:09.361 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 18:26:09.361 INFO kablam! 
Nov 01 18:26:09.362 INFO kablam! For more information on this warning you can consult
Nov 01 18:26:09.362 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 18:26:09.362 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 01 18:26:09.362 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 01 18:26:09.363 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 01 18:26:09.363 INFO kablam! files will be included as a benchmark target:
Nov 01 18:26:09.363 INFO kablam! 
Nov 01 18:26:09.363 INFO kablam! * /source/benches/compact1.rs
Nov 01 18:26:09.364 INFO kablam! * /source/benches/type2.rs
Nov 01 18:26:09.364 INFO kablam! 
Nov 01 18:26:09.364 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 01 18:26:09.364 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 01 18:26:09.365 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 01 18:26:09.365 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 01 18:26:09.365 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 01 18:26:09.367 INFO kablam! 
Nov 01 18:26:09.367 INFO kablam! For more information on this warning you can consult
Nov 01 18:26:09.367 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 01 18:26:09.368 INFO kablam!     Checking postscript v0.13.2 (/source)
Nov 01 18:26:11.819 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.50s
Nov 01 18:26:11.840 INFO kablam! su: No module specific data is present
Nov 01 18:26:12.814 INFO running `"docker" "rm" "-f" "05158c4b7df542c0c969a0d37628928d3f7cdc98c7da203535d2ed2d4c22117f"`
Nov 01 18:26:13.164 INFO blam! 05158c4b7df542c0c969a0d37628928d3f7cdc98c7da203535d2ed2d4c22117f