[INFO] crate postscript 0.13.2 is already in cache
[INFO] extracting crate postscript 0.13.2 into work/ex/pr-60039-1/sources/master#e305df1846a6d985315917ae0c81b74af8b4e641/reg/postscript/0.13.2
[INFO] extracting crate postscript 0.13.2 into work/ex/pr-60039-1/sources/try#99a7498759a22b5684caf798a98b7e90ad9d2443/reg/postscript/0.13.2
[INFO] validating manifest of postscript-0.13.2 on toolchain master#e305df1846a6d985315917ae0c81b74af8b4e641
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+e305df1846a6d985315917ae0c81b74af8b4e641-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] validating manifest of postscript-0.13.2 on toolchain try#99a7498759a22b5684caf798a98b7e90ad9d2443
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+99a7498759a22b5684caf798a98b7e90ad9d2443-alt" "read-manifest" "--manifest-path" "Cargo.toml"`
[INFO] started frobbing postscript-0.13.2
[INFO] removed 0 missing tests
[INFO] finished frobbing postscript-0.13.2
[INFO] frobbed toml for postscript-0.13.2 written to work/ex/pr-60039-1/sources/master#e305df1846a6d985315917ae0c81b74af8b4e641/reg/postscript/0.13.2/Cargo.toml
[INFO] started frobbing postscript-0.13.2
[INFO] removed 0 missing tests
[INFO] finished frobbing postscript-0.13.2
[INFO] frobbed toml for postscript-0.13.2 written to work/ex/pr-60039-1/sources/try#99a7498759a22b5684caf798a98b7e90ad9d2443/reg/postscript/0.13.2/Cargo.toml
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+e305df1846a6d985315917ae0c81b74af8b4e641-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+99a7498759a22b5684caf798a98b7e90ad9d2443-alt" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+e305df1846a6d985315917ae0c81b74af8b4e641-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] running `"/mnt/big/crater/work/local/cargo-home/bin/cargo" "+99a7498759a22b5684caf798a98b7e90ad9d2443-alt" "fetch" "--locked" "--manifest-path" "Cargo.toml"`
[INFO] checking postscript-0.13.2 against master#e305df1846a6d985315917ae0c81b74af8b4e641 for pr-60039-1
[INFO] running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-60039-1/worker-0/master#e305df1846a6d985315917ae0c81b74af8b4e641:/opt/crater/target:rw,Z" "-v" "/mnt/big/crater/work/ex/pr-60039-1/sources/master#e305df1846a6d985315917ae0c81b74af8b4e641/reg/postscript/0.13.2:/opt/crater/workdir:ro,Z" "-v" "/mnt/big/crater/work/local/cargo-home:/opt/crater/cargo-home:ro,Z" "-v" "/mnt/big/crater/work/local/rustup-home:/opt/crater/rustup-home:ro,Z" "-e" "USER_ID=1000" "-e" "SOURCE_DIR=/opt/crater/workdir" "-e" "MAP_USER_ID=1000" "-e" "CARGO_TARGET_DIR=/opt/crater/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/crater/cargo-home" "-e" "RUSTUP_HOME=/opt/crater/rustup-home" "-w" "/opt/crater/workdir" "-m" "1536M" "--network" "none" "rustops/crates-build-env" "/opt/crater/cargo-home/bin/cargo" "+e305df1846a6d985315917ae0c81b74af8b4e641-alt" "check" "--frozen" "--all" "--all-targets"`
[INFO] [stdout] de53f192a1df76abd2113ed46406445bfd2cdca6df2427558a82fa7db36a975c
[INFO] running `"docker" "start" "-a" "de53f192a1df76abd2113ed46406445bfd2cdca6df2427558a82fa7db36a975c"`
[INFO] [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other test targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a test target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/tests/type2.rs
[INFO] [stderr] * /opt/crater/workdir/tests/compact1.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a test target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autotests = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
[INFO] [stderr] disables Cargo from automatically inferring other benchmark targets.
[INFO] [stderr] This inference behavior will change in the Rust 2018 edition and the following
[INFO] [stderr] files will be included as a benchmark target:
[INFO] [stderr] 
[INFO] [stderr] * /opt/crater/workdir/benches/type2.rs
[INFO] [stderr] * /opt/crater/workdir/benches/compact1.rs
[INFO] [stderr] 
[INFO] [stderr] This is likely to break cargo build or cargo test as these files may not be
[INFO] [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
[INFO] [stderr] and disable this warning by adding `autobenches = false` to your [package]
[INFO] [stderr] section. You may also move the files to a location where Cargo would not
[INFO] [stderr] automatically infer them to be a target, such as in subfolders.
[INFO] [stderr] 
[INFO] [stderr] For more information on this warning you can consult
[INFO] [stderr] https://github.com/rust-lang/cargo/issues/5330
[INFO] [stderr]     Checking postscript v0.13.2 (/opt/crater/workdir)
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.92s
[INFO] running `"docker" "inspect" "de53f192a1df76abd2113ed46406445bfd2cdca6df2427558a82fa7db36a975c"`
[INFO] running `"docker" "rm" "-f" "de53f192a1df76abd2113ed46406445bfd2cdca6df2427558a82fa7db36a975c"`
[INFO] [stdout] de53f192a1df76abd2113ed46406445bfd2cdca6df2427558a82fa7db36a975c