Nov 28 12:29:42.264 INFO documenting libimagentryutil-0.9.0 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318
Nov 28 12:29:42.264 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-6/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-6/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:29:42.768 INFO [stdout] 363b475bce585f5086de56136f9ef0c4f57a7926439e343c4094f261423bfe29
Nov 28 12:29:42.770 INFO running `"docker" "start" "-a" "363b475bce585f5086de56136f9ef0c4f57a7926439e343c4094f261423bfe29"`
Nov 28 12:29:44.534 INFO [stderr] usermod: no changes
Nov 28 12:29:44.789 INFO [stderr]  Documenting libimagentryutil v0.9.0 (/source)
Nov 28 12:29:49.571 INFO [stderr] warning: `[::trace::trace_error]` cannot be resolved, ignoring it...
Nov 28 12:29:49.571 INFO [stderr]   --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/libimagerror-0.9.0/src/iter.rs:89:63
Nov 28 12:29:49.571 INFO [stderr]    |
Nov 28 12:29:49.571 INFO [stderr] 89 |     /// items. Each filtered `Err` will be trace-logged with [`::trace::trace_error`].
Nov 28 12:29:49.571 INFO [stderr]    |                                                               ^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Nov 28 12:29:49.571 INFO [stderr]    |
Nov 28 12:29:49.571 INFO [stderr]    = note: #[warn(intra_doc_link_resolution_failure)] on by default
Nov 28 12:29:49.571 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Nov 28 12:29:49.571 INFO [stderr] 
Nov 28 12:29:49.571 INFO [stderr] warning: `[0]` cannot be resolved, ignoring it...
Nov 28 12:29:49.571 INFO [stderr]   --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/toml-query-0.8.0/src/insert.rs:13:5
Nov 28 12:29:49.571 INFO [stderr]    |
Nov 28 12:29:49.571 INFO [stderr] 13 | /     /// Extension function for inserting a value in the current toml::Value document
Nov 28 12:29:49.571 INFO [stderr] 14 | |     /// using a custom seperator.
Nov 28 12:29:49.571 INFO [stderr] 15 | |     ///
Nov 28 12:29:49.571 INFO [stderr] 16 | |     /// For difference to TomlSetExt::set() and friends, read [#semantics].
Nov 28 12:29:49.571 INFO [stderr] ...  |
Nov 28 12:29:49.571 INFO [stderr] 79 | |     /// ```
Nov 28 12:29:49.571 INFO [stderr] 80 | |     ///
Nov 28 12:29:49.571 INFO [stderr]    | |_______^
Nov 28 12:29:49.571 INFO [stderr]    |
Nov 28 12:29:49.571 INFO [stderr]    = note: the link appears in this line:
Nov 28 12:29:49.571 INFO [stderr]            
Nov 28 12:29:49.571 INFO [stderr]             This is a known bug. So queries like "foo.bar.[0].baz" (or any query which has an array
Nov 28 12:29:49.571 INFO [stderr]                                                            ^
Nov 28 12:29:49.571 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Nov 28 12:29:49.571 INFO [stderr] 
Nov 28 12:29:49.691 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 5.12s
Nov 28 12:29:49.711 INFO [stderr] su: No module specific data is present
Nov 28 12:29:50.452 INFO running `"docker" "inspect" "363b475bce585f5086de56136f9ef0c4f57a7926439e343c4094f261423bfe29"`
Nov 28 12:29:50.717 INFO running `"docker" "rm" "-f" "363b475bce585f5086de56136f9ef0c4f57a7926439e343c4094f261423bfe29"`
Nov 28 12:29:50.948 INFO [stdout] 363b475bce585f5086de56136f9ef0c4f57a7926439e343c4094f261423bfe29