Nov 28 10:51:56.009 INFO documenting postscript-0.13.2 against master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb for pr-55318
Nov 28 10:51:56.010 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-0/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/pr-55318/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/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 +6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb-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"`
Nov 28 10:51:56.235 INFO [stdout] 88b8ae3cc7d210746878251950fe27dad970ad68a1553fc4ec67e60c26d25b8e
Nov 28 10:51:56.237 INFO running `"docker" "start" "-a" "88b8ae3cc7d210746878251950fe27dad970ad68a1553fc4ec67e60c26d25b8e"`
Nov 28 10:51:56.623 INFO [stderr] usermod: no changes
Nov 28 10:51:56.663 INFO [stderr] warning: An explicit [[test]] section is specified in Cargo.toml which currently
Nov 28 10:51:56.663 INFO [stderr] disables Cargo from automatically inferring other test targets.
Nov 28 10:51:56.663 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 28 10:51:56.663 INFO [stderr] files will be included as a test target:
Nov 28 10:51:56.663 INFO [stderr] 
Nov 28 10:51:56.663 INFO [stderr] * /source/tests/compact1.rs
Nov 28 10:51:56.664 INFO [stderr] * /source/tests/type2.rs
Nov 28 10:51:56.664 INFO [stderr] 
Nov 28 10:51:56.664 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 28 10:51:56.664 INFO [stderr] ready to be compiled as a test target today. You can future-proof yourself
Nov 28 10:51:56.664 INFO [stderr] and disable this warning by adding `autotests = false` to your [package]
Nov 28 10:51:56.664 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 28 10:51:56.664 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 28 10:51:56.664 INFO [stderr] 
Nov 28 10:51:56.664 INFO [stderr] For more information on this warning you can consult
Nov 28 10:51:56.664 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 28 10:51:56.664 INFO [stderr] warning: An explicit [[bench]] section is specified in Cargo.toml which currently
Nov 28 10:51:56.664 INFO [stderr] disables Cargo from automatically inferring other benchmark targets.
Nov 28 10:51:56.664 INFO [stderr] This inference behavior will change in the Rust 2018 edition and the following
Nov 28 10:51:56.664 INFO [stderr] files will be included as a benchmark target:
Nov 28 10:51:56.664 INFO [stderr] 
Nov 28 10:51:56.664 INFO [stderr] * /source/benches/compact1.rs
Nov 28 10:51:56.664 INFO [stderr] * /source/benches/type2.rs
Nov 28 10:51:56.664 INFO [stderr] 
Nov 28 10:51:56.664 INFO [stderr] This is likely to break cargo build or cargo test as these files may not be
Nov 28 10:51:56.664 INFO [stderr] ready to be compiled as a benchmark target today. You can future-proof yourself
Nov 28 10:51:56.664 INFO [stderr] and disable this warning by adding `autobenches = false` to your [package]
Nov 28 10:51:56.664 INFO [stderr] section. You may also move the files to a location where Cargo would not
Nov 28 10:51:56.664 INFO [stderr] automatically infer them to be a target, such as in subfolders.
Nov 28 10:51:56.664 INFO [stderr] 
Nov 28 10:51:56.664 INFO [stderr] For more information on this warning you can consult
Nov 28 10:51:56.664 INFO [stderr] https://github.com/rust-lang/cargo/issues/5330
Nov 28 10:51:56.668 INFO [stderr]  Documenting postscript v0.13.2 (/source)
Nov 28 10:51:58.377 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 1.67s
Nov 28 10:51:58.377 INFO [stderr] su: No module specific data is present
Nov 28 10:51:58.915 INFO running `"docker" "inspect" "88b8ae3cc7d210746878251950fe27dad970ad68a1553fc4ec67e60c26d25b8e"`
Nov 28 10:51:59.178 INFO running `"docker" "rm" "-f" "88b8ae3cc7d210746878251950fe27dad970ad68a1553fc4ec67e60c26d25b8e"`
Nov 28 10:51:59.451 INFO [stdout] 88b8ae3cc7d210746878251950fe27dad970ad68a1553fc4ec67e60c26d25b8e