Dec 02 06:05:38.057 INFO documenting libimagstore-0.9.0 against master#147e60c5f89cfa2d3ffc247413956a37582c98e7 for pr-55318-1
Dec 02 06:05:38.057 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-3/master#147e60c5f89cfa2d3ffc247413956a37582c98e7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-3/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 06:05:38.446 INFO [stdout] a899d80dde63b050042d2ecde7d4a1c3b020d42a5c26b9ef2d277b0bfeb3a041
Dec 02 06:05:38.456 INFO running `"docker" "start" "-a" "a899d80dde63b050042d2ecde7d4a1c3b020d42a5c26b9ef2d277b0bfeb3a041"`
Dec 02 06:05:39.867 INFO [stderr] usermod: no changes
Dec 02 06:05:40.105 INFO [stderr]  Documenting libimagstore v0.9.0 (/source)
Dec 02 06:05:44.495 INFO [stderr] warning: `[::trace::trace_error]` cannot be resolved, ignoring it...
Dec 02 06:05:44.495 INFO [stderr]   --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/libimagerror-0.9.0/src/iter.rs:89:63
Dec 02 06:05:44.495 INFO [stderr]    |
Dec 02 06:05:44.495 INFO [stderr] 89 |     /// items. Each filtered `Err` will be trace-logged with [`::trace::trace_error`].
Dec 02 06:05:44.496 INFO [stderr]    |                                                               ^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
Dec 02 06:05:44.496 INFO [stderr]    |
Dec 02 06:05:44.496 INFO [stderr]    = note: #[warn(intra_doc_link_resolution_failure)] on by default
Dec 02 06:05:44.496 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 06:05:44.496 INFO [stderr] 
Dec 02 06:05:44.496 INFO [stderr] warning: `[0]` cannot be resolved, ignoring it...
Dec 02 06:05:44.496 INFO [stderr]   --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/toml-query-0.8.0/src/insert.rs:13:5
Dec 02 06:05:44.496 INFO [stderr]    |
Dec 02 06:05:44.496 INFO [stderr] 13 | /     /// Extension function for inserting a value in the current toml::Value document
Dec 02 06:05:44.496 INFO [stderr] 14 | |     /// using a custom seperator.
Dec 02 06:05:44.496 INFO [stderr] 15 | |     ///
Dec 02 06:05:44.496 INFO [stderr] 16 | |     /// For difference to TomlSetExt::set() and friends, read [#semantics].
Dec 02 06:05:44.496 INFO [stderr] ...  |
Dec 02 06:05:44.496 INFO [stderr] 79 | |     /// ```
Dec 02 06:05:44.496 INFO [stderr] 80 | |     ///
Dec 02 06:05:44.496 INFO [stderr]    | |_______^
Dec 02 06:05:44.496 INFO [stderr]    |
Dec 02 06:05:44.496 INFO [stderr]    = note: the link appears in this line:
Dec 02 06:05:44.496 INFO [stderr]            
Dec 02 06:05:44.496 INFO [stderr]             This is a known bug. So queries like "foo.bar.[0].baz" (or any query which has an array
Dec 02 06:05:44.496 INFO [stderr]                                                            ^
Dec 02 06:05:44.496 INFO [stderr]    = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 06:05:44.496 INFO [stderr] 
Dec 02 06:05:44.686 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 4.79s
Dec 02 06:05:44.699 INFO [stderr] su: No module specific data is present
Dec 02 06:05:45.254 INFO running `"docker" "inspect" "a899d80dde63b050042d2ecde7d4a1c3b020d42a5c26b9ef2d277b0bfeb3a041"`
Dec 02 06:05:45.508 INFO running `"docker" "rm" "-f" "a899d80dde63b050042d2ecde7d4a1c3b020d42a5c26b9ef2d277b0bfeb3a041"`
Dec 02 06:05:45.744 INFO [stdout] a899d80dde63b050042d2ecde7d4a1c3b020d42a5c26b9ef2d277b0bfeb3a041