Nov 10 01:57:57.457 INFO checking postscript-0.13.2 against master#653da4fd006c97625247acd7e076d0782cdc149b for pr-55632
Nov 10 01:57:57.457 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55632/worker-2/master#653da4fd006c97625247acd7e076d0782cdc149b:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-2/pr-55632/master#653da4fd006c97625247acd7e076d0782cdc149b:/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 +653da4fd006c97625247acd7e076d0782cdc149b-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 10 01:57:57.827 INFO blam! 3d956d81792b30522030f808307c6bab9c762c8a7b06272d9fc0c36ac2ae353f
Nov 10 01:57:57.835 INFO running `"docker" "start" "-a" "3d956d81792b30522030f808307c6bab9c762c8a7b06272d9fc0c36ac2ae353f"`
Nov 10 01:57:58.381 INFO kablam! usermod: no changes
Nov 10 01:57:58.423 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 10 01:57:58.423 INFO kablam! disables Cargo from automatically inferring other test targets.
Nov 10 01:57:58.423 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 10 01:57:58.423 INFO kablam! files will be included as a test target:
Nov 10 01:57:58.423 INFO kablam! 
Nov 10 01:57:58.423 INFO kablam! * /source/tests/compact1.rs
Nov 10 01:57:58.423 INFO kablam! * /source/tests/type2.rs
Nov 10 01:57:58.423 INFO kablam! 
Nov 10 01:57:58.423 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 10 01:57:58.423 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Nov 10 01:57:58.423 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Nov 10 01:57:58.423 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 10 01:57:58.423 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 10 01:57:58.423 INFO kablam! 
Nov 10 01:57:58.423 INFO kablam! For more information on this warning you can consult
Nov 10 01:57:58.423 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 10 01:57:58.423 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 10 01:57:58.423 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 10 01:57:58.423 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 10 01:57:58.423 INFO kablam! files will be included as a benchmark target:
Nov 10 01:57:58.423 INFO kablam! 
Nov 10 01:57:58.423 INFO kablam! * /source/benches/compact1.rs
Nov 10 01:57:58.423 INFO kablam! * /source/benches/type2.rs
Nov 10 01:57:58.423 INFO kablam! 
Nov 10 01:57:58.423 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 10 01:57:58.423 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 10 01:57:58.423 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 10 01:57:58.423 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 10 01:57:58.423 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 10 01:57:58.423 INFO kablam! 
Nov 10 01:57:58.423 INFO kablam! For more information on this warning you can consult
Nov 10 01:57:58.423 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 10 01:57:58.435 INFO kablam!     Checking postscript v0.13.2 (/source)
Nov 10 01:58:01.054 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.65s
Nov 10 01:58:01.056 INFO kablam! su: No module specific data is present
Nov 10 01:58:01.687 INFO running `"docker" "rm" "-f" "3d956d81792b30522030f808307c6bab9c762c8a7b06272d9fc0c36ac2ae353f"`
Nov 10 01:58:02.019 INFO blam! 3d956d81792b30522030f808307c6bab9c762c8a7b06272d9fc0c36ac2ae353f