Nov 04 19:39:44.507 INFO checking postscript-0.13.2 against try#e740b9aa0b624fa39feb39613e76d15bdf57e594 for pr-55655
Nov 04 19:39:44.507 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55655/worker-7/try#e740b9aa0b624fa39feb39613e76d15bdf57e594:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-55655/try#e740b9aa0b624fa39feb39613e76d15bdf57e594:/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 +e740b9aa0b624fa39feb39613e76d15bdf57e594-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 04 19:39:44.694 INFO blam! 6ee6c75039cf1fde5f6f5a0aedf9047df3c406cde49efaa7d267443dfd078882
Nov 04 19:39:44.696 INFO running `"docker" "start" "-a" "6ee6c75039cf1fde5f6f5a0aedf9047df3c406cde49efaa7d267443dfd078882"`
Nov 04 19:39:45.311 INFO kablam! usermod: no changes
Nov 04 19:39:45.332 INFO kablam! warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 04 19:39:45.332 INFO kablam! disables Cargo from automatically inferring other test targets.
Nov 04 19:39:45.332 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 04 19:39:45.332 INFO kablam! files will be included as a test target:
Nov 04 19:39:45.332 INFO kablam! 
Nov 04 19:39:45.332 INFO kablam! * /source/tests/compact1.rs
Nov 04 19:39:45.332 INFO kablam! * /source/tests/type2.rs
Nov 04 19:39:45.332 INFO kablam! 
Nov 04 19:39:45.332 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 04 19:39:45.333 INFO kablam! ready to be compiled as a test target today. You can future-proof yourself
Nov 04 19:39:45.333 INFO kablam! and disable this warning by adding `autotests = false` to your [package]
Nov 04 19:39:45.333 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 04 19:39:45.333 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 04 19:39:45.333 INFO kablam! 
Nov 04 19:39:45.333 INFO kablam! For more information on this warning you can consult
Nov 04 19:39:45.333 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 04 19:39:45.333 INFO kablam! warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 04 19:39:45.333 INFO kablam! disables Cargo from automatically inferring other benchmark targets.
Nov 04 19:39:45.333 INFO kablam! This inference behavior will change in the Rust 2018 edition and the following
Nov 04 19:39:45.333 INFO kablam! files will be included as a benchmark target:
Nov 04 19:39:45.333 INFO kablam! 
Nov 04 19:39:45.333 INFO kablam! * /source/benches/compact1.rs
Nov 04 19:39:45.333 INFO kablam! * /source/benches/type2.rs
Nov 04 19:39:45.333 INFO kablam! 
Nov 04 19:39:45.334 INFO kablam! This is likely to break cargo build or cargo test as these files may not be
Nov 04 19:39:45.334 INFO kablam! ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 04 19:39:45.334 INFO kablam! and disable this warning by adding `autobenches = false` to your [package]
Nov 04 19:39:45.334 INFO kablam! section. You may also move the files to a location where Cargo would not
Nov 04 19:39:45.334 INFO kablam! automatically infer them to be a target, such as in subfolders.
Nov 04 19:39:45.334 INFO kablam! 
Nov 04 19:39:45.334 INFO kablam! For more information on this warning you can consult
Nov 04 19:39:45.334 INFO kablam! https://github.com/rust-lang/cargo/issues/5330
Nov 04 19:39:45.342 INFO kablam!     Checking postscript v0.13.2 (/source)
Nov 04 19:39:47.863 INFO kablam!     Finished dev [unoptimized + debuginfo] target(s) in 2.53s
Nov 04 19:39:47.869 INFO kablam! su: No module specific data is present
Nov 04 19:39:48.483 INFO running `"docker" "rm" "-f" "6ee6c75039cf1fde5f6f5a0aedf9047df3c406cde49efaa7d267443dfd078882"`
Nov 04 19:39:48.819 INFO blam! 6ee6c75039cf1fde5f6f5a0aedf9047df3c406cde49efaa7d267443dfd078882