Dec 02 03:48:02.652 INFO documenting rorschach-0.1.3 against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1
Dec 02 03:48:02.652 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 03:48:03.032 INFO [stdout] 5e78fa2eb0dd2c08457f23c174ebc9fefe3b6a3fcd140bf78502a8cf92b13ce7
Dec 02 03:48:03.038 INFO running `"docker" "start" "-a" "5e78fa2eb0dd2c08457f23c174ebc9fefe3b6a3fcd140bf78502a8cf92b13ce7"`
Dec 02 03:48:04.531 INFO [stderr] usermod: no changes
Dec 02 03:48:04.628 INFO [stderr]     Checking ansi_term v0.8.0
Dec 02 03:48:05.193 INFO [stderr]  Documenting rorschach v0.1.3 (/source)
Dec 02 03:48:06.980 INFO [stderr] warning: `[cc]` cannot be resolved, ignoring it...
Dec 02 03:48:06.980 INFO [stderr]    --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/ansi_term-0.8.0/src/lib.rs:272:62
Dec 02 03:48:06.980 INFO [stderr]     |
Dec 02 03:48:06.980 INFO [stderr] 272 |     /// It might make more sense to look at a [colour chart][cc].
Dec 02 03:48:06.980 INFO [stderr]     |                                                              ^^ cannot be resolved, ignoring
Dec 02 03:48:06.980 INFO [stderr]     |
Dec 02 03:48:06.980 INFO [stderr]     = note: #[warn(intra_doc_link_resolution_failure)] on by default
Dec 02 03:48:06.980 INFO [stderr]     = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 03:48:06.980 INFO [stderr] 
Dec 02 03:48:06.980 INFO [stderr] warning: `[cc]` cannot be resolved, ignoring it...
Dec 02 03:48:06.980 INFO [stderr]    --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/ansi_term-0.8.0/src/lib.rs:272:62
Dec 02 03:48:06.980 INFO [stderr]     |
Dec 02 03:48:06.980 INFO [stderr] 272 |     /// It might make more sense to look at a [colour chart][cc].
Dec 02 03:48:06.980 INFO [stderr]     |                                                              ^^ cannot be resolved, ignoring
Dec 02 03:48:06.980 INFO [stderr]     |
Dec 02 03:48:06.980 INFO [stderr]     = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 03:48:06.980 INFO [stderr] 
Dec 02 03:48:06.980 INFO [stderr] warning: `[cc]` cannot be resolved, ignoring it...
Dec 02 03:48:06.980 INFO [stderr]    --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/ansi_term-0.8.0/src/lib.rs:273:10
Dec 02 03:48:06.980 INFO [stderr]     |
Dec 02 03:48:06.980 INFO [stderr] 273 |     /// [cc]: https://upload.wikimedia.org/wikipedia/en/1/15/Xterm_256color_chart.svg
Dec 02 03:48:06.980 INFO [stderr]     |          ^^ cannot be resolved, ignoring
Dec 02 03:48:06.980 INFO [stderr]     |
Dec 02 03:48:06.981 INFO [stderr]     = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 03:48:06.981 INFO [stderr] 
Dec 02 03:48:07.075 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.51s
Dec 02 03:48:07.082 INFO [stderr] su: No module specific data is present
Dec 02 03:48:08.092 INFO running `"docker" "inspect" "5e78fa2eb0dd2c08457f23c174ebc9fefe3b6a3fcd140bf78502a8cf92b13ce7"`
Dec 02 03:48:08.410 INFO running `"docker" "rm" "-f" "5e78fa2eb0dd2c08457f23c174ebc9fefe3b6a3fcd140bf78502a8cf92b13ce7"`
Dec 02 03:48:08.749 INFO [stdout] 5e78fa2eb0dd2c08457f23c174ebc9fefe3b6a3fcd140bf78502a8cf92b13ce7