Dec 02 05:56:23.666 INFO documenting lojidoc-0.3.1 against try#f86f76f89ea2b1ccbfb3741962ec2029d878a389 for pr-55318-1 Dec 02 05:56:23.666 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 05:56:23.970 INFO [stdout] 2315c56ee473809f0edae78352ebd1b11581b3c77a9cb833de0e9bf2400306a1 Dec 02 05:56:23.976 INFO running `"docker" "start" "-a" "2315c56ee473809f0edae78352ebd1b11581b3c77a9cb833de0e9bf2400306a1"` Dec 02 05:56:24.888 INFO [stderr] usermod: no changes Dec 02 05:56:25.369 INFO [stderr] Checking libgit2-sys v0.7.10 Dec 02 05:56:25.370 INFO [stderr] Checking mdbook v0.2.2 Dec 02 05:56:26.124 INFO [stderr] Checking git2 v0.7.5 Dec 02 05:56:32.331 INFO [stderr] Documenting lojidoc v0.3.1 (/source) Dec 02 05:56:40.080 INFO [stderr] warning: `[0]` cannot be resolved, ignoring it... Dec 02 05:56:40.081 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/toml-query-0.7.0/src/insert.rs:13:5 Dec 02 05:56:40.081 INFO [stderr] | Dec 02 05:56:40.081 INFO [stderr] 13 | / /// Extension function for inserting a value in the current toml::Value document Dec 02 05:56:40.082 INFO [stderr] 14 | | /// using a custom seperator. Dec 02 05:56:40.082 INFO [stderr] 15 | | /// Dec 02 05:56:40.082 INFO [stderr] 16 | | /// For difference to TomlSetExt::set() and friends, read [#semantics]. Dec 02 05:56:40.082 INFO [stderr] ... | Dec 02 05:56:40.082 INFO [stderr] 79 | | /// ``` Dec 02 05:56:40.082 INFO [stderr] 80 | | /// Dec 02 05:56:40.082 INFO [stderr] | |_______^ Dec 02 05:56:40.082 INFO [stderr] | Dec 02 05:56:40.082 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Dec 02 05:56:40.082 INFO [stderr] = note: the link appears in this line: Dec 02 05:56:40.082 INFO [stderr] Dec 02 05:56:40.082 INFO [stderr] This is a known bug. So queries like "foo.bar.[0].baz" (or any query which has an array Dec 02 05:56:40.082 INFO [stderr] ^ Dec 02 05:56:40.082 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Dec 02 05:56:40.082 INFO [stderr] Dec 02 05:56:40.230 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 15.34s Dec 02 05:56:40.264 INFO [stderr] su: No module specific data is present Dec 02 05:56:40.880 INFO running `"docker" "inspect" "2315c56ee473809f0edae78352ebd1b11581b3c77a9cb833de0e9bf2400306a1"` Dec 02 05:56:41.164 INFO running `"docker" "rm" "-f" "2315c56ee473809f0edae78352ebd1b11581b3c77a9cb833de0e9bf2400306a1"` Dec 02 05:56:41.464 INFO [stdout] 2315c56ee473809f0edae78352ebd1b11581b3c77a9cb833de0e9bf2400306a1