Dec 02 04:26:41.523 INFO documenting procinfo-0.4.2 against master#147e60c5f89cfa2d3ffc247413956a37582c98e7 for pr-55318-1 Dec 02 04:26:41.523 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-4/master#147e60c5f89cfa2d3ffc247413956a37582c98e7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/pr-55318-1/master#147e60c5f89cfa2d3ffc247413956a37582c98e7:/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 +147e60c5f89cfa2d3ffc247413956a37582c98e7-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:26:41.883 INFO [stdout] 870bcc50695f2eab3c638956c05af07285a9d2e50957e274e5a5671ce6cce716 Dec 02 04:26:41.886 INFO running `"docker" "start" "-a" "870bcc50695f2eab3c638956c05af07285a9d2e50957e274e5a5671ce6cce716"` Dec 02 04:26:43.144 INFO [stderr] usermod: no changes Dec 02 04:26:43.260 INFO [stderr] Compiling procinfo v0.4.2 (/source) Dec 02 04:26:44.300 INFO [stderr] Documenting procinfo v0.4.2 (/source) Dec 02 04:26:46.800 INFO [stderr] warning: `[pid]` cannot be resolved, ignoring it... Dec 02 04:26:46.800 INFO [stderr] --> src/pid/stat.rs:116:39 Dec 02 04:26:46.800 INFO [stderr] | Dec 02 04:26:46.800 INFO [stderr] 116 | /// real-time signals; use /proc/[pid]/status instead. Dec 02 04:26:46.800 INFO [stderr] | ^^^ cannot be resolved, ignoring Dec 02 04:26:46.800 INFO [stderr] | Dec 02 04:26:46.800 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Dec 02 04:26:46.800 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 04:26:46.800 INFO [stderr] Dec 02 04:26:46.808 INFO [stderr] warning: `[pid]` cannot be resolved, ignoring it... Dec 02 04:26:46.808 INFO [stderr] --> src/pid/stat.rs:116:39 Dec 02 04:26:46.808 INFO [stderr] | Dec 02 04:26:46.808 INFO [stderr] 116 | /// real-time signals; use /proc/[pid]/status instead. Dec 02 04:26:46.808 INFO [stderr] | ^^^ cannot be resolved, ignoring Dec 02 04:26:46.808 INFO [stderr] | Dec 02 04:26:46.808 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 04:26:46.808 INFO [stderr] Dec 02 04:26:46.942 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 3.76s Dec 02 04:26:46.952 INFO [stderr] su: No module specific data is present Dec 02 04:26:47.600 INFO running `"docker" "inspect" "870bcc50695f2eab3c638956c05af07285a9d2e50957e274e5a5671ce6cce716"` Dec 02 04:26:47.902 INFO running `"docker" "rm" "-f" "870bcc50695f2eab3c638956c05af07285a9d2e50957e274e5a5671ce6cce716"` Dec 02 04:26:48.158 INFO [stdout] 870bcc50695f2eab3c638956c05af07285a9d2e50957e274e5a5671ce6cce716