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