Dec 02 04:26:41.362 INFO documenting procinfo-0.4.2 against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1 Dec 02 04:26:41.362 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-0/try#f86f76f89ea2b1ccbfb3741962ec2029d878a389:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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:26:41.748 INFO [stdout] 64f1961883361b74e51ec835309bd65e0cd953d864077ac20162cd85187cc530 Dec 02 04:26:41.756 INFO running `"docker" "start" "-a" "64f1961883361b74e51ec835309bd65e0cd953d864077ac20162cd85187cc530"` Dec 02 04:26:42.718 INFO [stderr] usermod: no changes Dec 02 04:26:42.795 INFO [stderr] Compiling procinfo v0.4.2 (/source) Dec 02 04:26:44.056 INFO [stderr] Documenting procinfo v0.4.2 (/source) Dec 02 04:26:46.591 INFO [stderr] warning: `[pid]` cannot be resolved, ignoring it... Dec 02 04:26:46.591 INFO [stderr] --> src/pid/stat.rs:116:39 Dec 02 04:26:46.591 INFO [stderr] | Dec 02 04:26:46.591 INFO [stderr] 116 | /// real-time signals; use /proc/[pid]/status instead. Dec 02 04:26:46.591 INFO [stderr] | ^^^ cannot be resolved, ignoring Dec 02 04:26:46.591 INFO [stderr] | Dec 02 04:26:46.591 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Dec 02 04:26:46.591 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 04:26:46.591 INFO [stderr] Dec 02 04:26:46.592 INFO [stderr] warning: `[pid]` cannot be resolved, ignoring it... Dec 02 04:26:46.593 INFO [stderr] --> src/pid/stat.rs:116:39 Dec 02 04:26:46.593 INFO [stderr] | Dec 02 04:26:46.593 INFO [stderr] 116 | /// real-time signals; use /proc/[pid]/status instead. Dec 02 04:26:46.593 INFO [stderr] | ^^^ cannot be resolved, ignoring Dec 02 04:26:46.600 INFO [stderr] | Dec 02 04:26:46.600 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 04:26:46.600 INFO [stderr] Dec 02 04:26:46.756 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 4.01s Dec 02 04:26:46.762 INFO [stderr] su: No module specific data is present Dec 02 04:26:47.471 INFO running `"docker" "inspect" "64f1961883361b74e51ec835309bd65e0cd953d864077ac20162cd85187cc530"` Dec 02 04:26:47.722 INFO running `"docker" "rm" "-f" "64f1961883361b74e51ec835309bd65e0cd953d864077ac20162cd85187cc530"` Dec 02 04:26:48.024 INFO [stdout] 64f1961883361b74e51ec835309bd65e0cd953d864077ac20162cd85187cc530