Dec 02 04:30:12.554 INFO documenting postscript-0.13.2 against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1
Dec 02 04:30:12.554 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-7/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/pr-55318-1/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/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 +f86f76f89ea2b1ccbfb3741962ec2029d878a389-alt doc --frozen --no-deps --document-private-items" "-e" "CARGO_TARGET_DIR=/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/cargo-home" "-e" "RUSTUP_HOME=/rustup-home" "-m" "1536M" "--network" "none" "crater"`
Dec 02 04:30:12.752 INFO [stdout] 4875aa3c8a976bb2a9aed1055a98fde3f248b43448b1d20feb150c6ae52e8c3b
Dec 02 04:30:12.754 INFO running `"docker" "start" "-a" "4875aa3c8a976bb2a9aed1055a98fde3f248b43448b1d20feb150c6ae52e8c3b"`
Dec 02 04:30:13.155 INFO [stderr] usermod: no changes
Dec 02 04:30:13.181 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Dec 02 04:30:13.181 INFO [stderr] disables Cargo from automatically inferring other test targets.
Dec 02 04:30:13.181 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 04:30:13.181 INFO [stderr] files will be included as a test target:
Dec 02 04:30:13.181 INFO [stderr] 
Dec 02 04:30:13.181 INFO [stderr] * /source/tests/compact1.rs
Dec 02 04:30:13.181 INFO [stderr] * /source/tests/type2.rs
Dec 02 04:30:13.181 INFO [stderr] 
Dec 02 04:30:13.181 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 04:30:13.181 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Dec 02 04:30:13.181 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Dec 02 04:30:13.181 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 04:30:13.181 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 04:30:13.181 INFO [stderr] 
Dec 02 04:30:13.181 INFO [stderr] For more information on this warning you can consult
Dec 02 04:30:13.181 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 04:30:13.181 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Dec 02 04:30:13.181 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Dec 02 04:30:13.181 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Dec 02 04:30:13.181 INFO [stderr] files will be included as a benchmark target:
Dec 02 04:30:13.181 INFO [stderr] 
Dec 02 04:30:13.181 INFO [stderr] * /source/benches/compact1.rs
Dec 02 04:30:13.181 INFO [stderr] * /source/benches/type2.rs
Dec 02 04:30:13.181 INFO [stderr] 
Dec 02 04:30:13.181 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Dec 02 04:30:13.181 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Dec 02 04:30:13.181 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Dec 02 04:30:13.181 INFO [stderr] section. You may also move the files to a location where Cargo would not
Dec 02 04:30:13.181 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Dec 02 04:30:13.182 INFO [stderr] 
Dec 02 04:30:13.182 INFO [stderr] For more information on this warning you can consult
Dec 02 04:30:13.182 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Dec 02 04:30:13.182 INFO [stderr]  Documenting postscript v0.13.2 (/source)
Dec 02 04:30:14.861 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.69s
Dec 02 04:30:14.862 INFO [stderr] su: No module specific data is present
Dec 02 04:30:15.258 INFO running `"docker" "inspect" "4875aa3c8a976bb2a9aed1055a98fde3f248b43448b1d20feb150c6ae52e8c3b"`
Dec 02 04:30:15.542 INFO running `"docker" "rm" "-f" "4875aa3c8a976bb2a9aed1055a98fde3f248b43448b1d20feb150c6ae52e8c3b"`
Dec 02 04:30:15.871 INFO [stdout] 4875aa3c8a976bb2a9aed1055a98fde3f248b43448b1d20feb150c6ae52e8c3b