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