Nov 28 12:29:25.691 INFO documenting libimagstore-0.9.0 against master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb for pr-55318 Nov 28 12:29:25.692 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-1/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/pr-55318/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/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 +6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb-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:26.084 INFO [stdout] dcc24d0f461ad8eea148ed054f86c8683e08b0ebf6b1a3821313e4e37718bd02 Nov 28 12:29:26.087 INFO running `"docker" "start" "-a" "dcc24d0f461ad8eea148ed054f86c8683e08b0ebf6b1a3821313e4e37718bd02"` Nov 28 12:29:27.077 INFO [stderr] usermod: no changes Nov 28 12:29:27.320 INFO [stderr] Checking boolinator v2.4.0 Nov 28 12:29:27.322 INFO [stderr] Checking libimagerror v0.9.0 Nov 28 12:29:27.323 INFO [stderr] Checking toml-query v0.8.0 Nov 28 12:29:28.077 INFO [stderr] Checking libimagutil v0.9.0 Nov 28 12:29:30.366 INFO [stderr] Documenting libimagstore v0.9.0 (/source) Nov 28 12:29:34.912 INFO [stderr] warning: `[::trace::trace_error]` cannot be resolved, ignoring it... Nov 28 12:29:34.912 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/libimagerror-0.9.0/src/iter.rs:89:63 Nov 28 12:29:34.912 INFO [stderr] | Nov 28 12:29:34.912 INFO [stderr] 89 | /// items. Each filtered `Err` will be trace-logged with [`::trace::trace_error`]. Nov 28 12:29:34.912 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 12:29:34.912 INFO [stderr] | Nov 28 12:29:34.912 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 12:29:34.912 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 12:29:34.912 INFO [stderr] Nov 28 12:29:34.914 INFO [stderr] warning: `[0]` cannot be resolved, ignoring it... Nov 28 12:29:34.914 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/toml-query-0.8.0/src/insert.rs:13:5 Nov 28 12:29:34.914 INFO [stderr] | Nov 28 12:29:34.914 INFO [stderr] 13 | / /// Extension function for inserting a value in the current toml::Value document Nov 28 12:29:34.914 INFO [stderr] 14 | | /// using a custom seperator. Nov 28 12:29:34.914 INFO [stderr] 15 | | /// Nov 28 12:29:34.914 INFO [stderr] 16 | | /// For difference to TomlSetExt::set() and friends, read [#semantics]. Nov 28 12:29:34.914 INFO [stderr] ... | Nov 28 12:29:34.914 INFO [stderr] 79 | | /// ``` Nov 28 12:29:34.914 INFO [stderr] 80 | | /// Nov 28 12:29:34.914 INFO [stderr] | |_______^ Nov 28 12:29:34.914 INFO [stderr] | Nov 28 12:29:34.914 INFO [stderr] = note: the link appears in this line: Nov 28 12:29:34.914 INFO [stderr] Nov 28 12:29:34.914 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:34.914 INFO [stderr] ^ Nov 28 12:29:34.914 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 12:29:34.914 INFO [stderr] Nov 28 12:29:35.125 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 8.03s Nov 28 12:29:35.143 INFO [stderr] su: No module specific data is present Nov 28 12:29:36.231 INFO running `"docker" "inspect" "dcc24d0f461ad8eea148ed054f86c8683e08b0ebf6b1a3821313e4e37718bd02"` Nov 28 12:29:36.393 INFO running `"docker" "rm" "-f" "dcc24d0f461ad8eea148ed054f86c8683e08b0ebf6b1a3821313e4e37718bd02"` Nov 28 12:29:36.564 INFO [stdout] dcc24d0f461ad8eea148ed054f86c8683e08b0ebf6b1a3821313e4e37718bd02