Nov 28 20:26:52.766 INFO checking postscript-0.13.2 against master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5 for pr-56074
Nov 28 20:26:52.768 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-56074/worker-0/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-56074/master#0b9f19dff1347e29bf4362ab5a8fab84b43023b5:/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 +0b9f19dff1347e29bf4362ab5a8fab84b43023b5-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 28 20:26:52.962 INFO [stdout] e3521414842547fabfe68dad5cc72a57ad1de294db7dfe25ca1dd90983b58916
Nov 28 20:26:52.966 INFO running `"docker" "start" "-a" "e3521414842547fabfe68dad5cc72a57ad1de294db7dfe25ca1dd90983b58916"`
Nov 28 20:26:53.545 INFO [stderr] usermod: no changes
Nov 28 20:26:53.563 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 28 20:26:53.563 INFO [stderr] disables Cargo from automatically inferring other test targets.
Nov 28 20:26:53.563 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 28 20:26:53.563 INFO [stderr] files will be included as a test target:
Nov 28 20:26:53.563 INFO [stderr] 
Nov 28 20:26:53.563 INFO [stderr] * /source/tests/compact1.rs
Nov 28 20:26:53.563 INFO [stderr] * /source/tests/type2.rs
Nov 28 20:26:53.563 INFO [stderr] 
Nov 28 20:26:53.563 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 28 20:26:53.563 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Nov 28 20:26:53.563 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Nov 28 20:26:53.597 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 28 20:26:53.598 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 28 20:26:53.598 INFO [stderr] 
Nov 28 20:26:53.598 INFO [stderr] For more information on this warning you can consult
Nov 28 20:26:53.598 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 28 20:26:53.598 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 28 20:26:53.598 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 28 20:26:53.598 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 28 20:26:53.598 INFO [stderr] files will be included as a benchmark target:
Nov 28 20:26:53.598 INFO [stderr] 
Nov 28 20:26:53.598 INFO [stderr] * /source/benches/compact1.rs
Nov 28 20:26:53.598 INFO [stderr] * /source/benches/type2.rs
Nov 28 20:26:53.598 INFO [stderr] 
Nov 28 20:26:53.598 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 28 20:26:53.598 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 28 20:26:53.598 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 28 20:26:53.598 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 28 20:26:53.598 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 28 20:26:53.598 INFO [stderr] 
Nov 28 20:26:53.598 INFO [stderr] For more information on this warning you can consult
Nov 28 20:26:53.598 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 28 20:26:53.598 INFO [stderr]     Checking postscript v0.13.2 (/source)
Nov 28 20:26:56.411 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.86s
Nov 28 20:26:56.414 INFO [stderr] su: No module specific data is present
Nov 28 20:26:57.375 INFO running `"docker" "inspect" "e3521414842547fabfe68dad5cc72a57ad1de294db7dfe25ca1dd90983b58916"`
Nov 28 20:26:57.761 INFO running `"docker" "rm" "-f" "e3521414842547fabfe68dad5cc72a57ad1de294db7dfe25ca1dd90983b58916"`
Nov 28 20:26:58.077 INFO [stdout] e3521414842547fabfe68dad5cc72a57ad1de294db7dfe25ca1dd90983b58916