Nov 28 12:30:28.185 INFO documenting libimagcounter-0.4.0 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318 Nov 28 12:30:28.185 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-5/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-5/pr-55318/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/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 +f5a0bd723553ea4b7556bd7087b9f0919cafb483-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 12:30:28.502 INFO [stdout] fa454f85ee15586bc11d428ae8c8ec3b879c40317f1c13d9f21623ce2ca182f9 Nov 28 12:30:28.504 INFO running `"docker" "start" "-a" "fa454f85ee15586bc11d428ae8c8ec3b879c40317f1c13d9f21623ce2ca182f9"` Nov 28 12:30:29.299 INFO [stderr] usermod: no changes Nov 28 12:30:29.474 INFO [stderr] Checking libimagerror v0.4.0 Nov 28 12:30:29.483 INFO [stderr] Checking libimagutil v0.4.0 Nov 28 12:30:29.483 INFO [stderr] Checking toml-query v0.3.1 Nov 28 12:30:31.167 INFO [stderr] Checking libimagstore v0.4.0 Nov 28 12:30:34.183 INFO [stderr] Documenting libimagcounter v0.4.0 (/source) Nov 28 12:30:38.095 INFO [stderr] warning: `[::trace::trace_error]` cannot be resolved, ignoring it... Nov 28 12:30:38.095 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/libimagerror-0.4.0/src/iter.rs:124:63 Nov 28 12:30:38.095 INFO [stderr] | Nov 28 12:30:38.095 INFO [stderr] 124 | /// items. Each filtered `Err` will be trace-logged with [`::trace::trace_error`]. Nov 28 12:30:38.096 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 12:30:38.096 INFO [stderr] | Nov 28 12:30:38.096 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 12:30:38.096 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 12:30:38.096 INFO [stderr] Nov 28 12:30:38.096 INFO [stderr] warning: `[0]` cannot be resolved, ignoring it... Nov 28 12:30:38.096 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/toml-query-0.3.1/src/insert.rs:11:5 Nov 28 12:30:38.096 INFO [stderr] | Nov 28 12:30:38.096 INFO [stderr] 11 | / /// Extension function for inserting a value in the current toml::Value document Nov 28 12:30:38.096 INFO [stderr] 12 | | /// using a custom seperator. Nov 28 12:30:38.096 INFO [stderr] 13 | | /// Nov 28 12:30:38.096 INFO [stderr] 14 | | /// For difference to TomlSetExt::set() and friends, read [#semantics]. Nov 28 12:30:38.096 INFO [stderr] ... | Nov 28 12:30:38.096 INFO [stderr] 77 | | /// ``` Nov 28 12:30:38.096 INFO [stderr] 78 | | /// Nov 28 12:30:38.096 INFO [stderr] | |_______^ Nov 28 12:30:38.096 INFO [stderr] | Nov 28 12:30:38.096 INFO [stderr] = note: the link appears in this line: Nov 28 12:30:38.096 INFO [stderr] Nov 28 12:30:38.096 INFO [stderr] This is a known bug. So queries like "foo.bar.[0].baz" (or any query which has an array Nov 28 12:30:38.096 INFO [stderr] ^ Nov 28 12:30:38.096 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 12:30:38.096 INFO [stderr] Nov 28 12:30:38.183 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 8.86s Nov 28 12:30:38.195 INFO [stderr] su: No module specific data is present Nov 28 12:30:38.511 INFO running `"docker" "inspect" "fa454f85ee15586bc11d428ae8c8ec3b879c40317f1c13d9f21623ce2ca182f9"` Nov 28 12:30:38.627 INFO running `"docker" "rm" "-f" "fa454f85ee15586bc11d428ae8c8ec3b879c40317f1c13d9f21623ce2ca182f9"` Nov 28 12:30:38.744 INFO [stdout] fa454f85ee15586bc11d428ae8c8ec3b879c40317f1c13d9f21623ce2ca182f9