Nov 28 16:07:13.504 INFO documenting bendy-0.1.2 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318 Nov 28 16:07:13.504 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-4/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-4/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 16:07:13.798 INFO [stdout] 458eefd0a79bc9f04c6bf2743682c76f87aa7bd9839cb6da5d0d1986fc0cb9d8 Nov 28 16:07:13.800 INFO running `"docker" "start" "-a" "458eefd0a79bc9f04c6bf2743682c76f87aa7bd9839cb6da5d0d1986fc0cb9d8"` Nov 28 16:07:14.278 INFO [stderr] usermod: no changes Nov 28 16:07:14.361 INFO [stderr] Documenting bendy v0.1.2 (/source) Nov 28 16:07:16.379 INFO [stderr] warning: `[Encodable]` cannot be resolved, ignoring it... Nov 28 16:07:16.379 INFO [stderr] --> src/encoder.rs:5:60 Nov 28 16:07:16.379 INFO [stderr] | Nov 28 16:07:16.379 INFO [stderr] 5 | //! The easiest way to encode a structure is to implement [`Encodable`] for it. For most structures, Nov 28 16:07:16.379 INFO [stderr] | ^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 16:07:16.379 INFO [stderr] | Nov 28 16:07:16.379 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 16:07:16.379 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 16:07:16.379 INFO [stderr] Nov 28 16:07:16.379 INFO [stderr] warning: `[Encodable::to_bytes]` cannot be resolved, ignoring it... Nov 28 16:07:16.379 INFO [stderr] --> src/encoder.rs:31:45 Nov 28 16:07:16.379 INFO [stderr] | Nov 28 16:07:16.379 INFO [stderr] 31 | //! Then, messages can be serialized using [`Encodable::to_bytes`]: Nov 28 16:07:16.379 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 16:07:16.379 INFO [stderr] | Nov 28 16:07:16.379 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 16:07:16.379 INFO [stderr] Nov 28 16:07:16.379 INFO [stderr] warning: `[Encodable]` cannot be resolved, ignoring it... Nov 28 16:07:16.379 INFO [stderr] --> src/encoder.rs:65:45 Nov 28 16:07:16.379 INFO [stderr] | Nov 28 16:07:16.379 INFO [stderr] 65 | //! Most primitive types already implement [`Encodable`]. Nov 28 16:07:16.379 INFO [stderr] | ^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 16:07:16.379 INFO [stderr] | Nov 28 16:07:16.379 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 16:07:16.379 INFO [stderr] Nov 28 16:07:16.379 INFO [stderr] warning: `[Encodable]` cannot be resolved, ignoring it... Nov 28 16:07:16.379 INFO [stderr] --> src/encoder.rs:69:76 Nov 28 16:07:16.379 INFO [stderr] | Nov 28 16:07:16.379 INFO [stderr] 69 | //! To allow this to be used on limited platforms, all implementations of [`Encodable`] include a Nov 28 16:07:16.379 INFO [stderr] | ^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 16:07:16.380 INFO [stderr] | Nov 28 16:07:16.380 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 16:07:16.380 INFO [stderr] Nov 28 16:07:16.380 INFO [stderr] warning: `[Encodable::encode]` cannot be resolved, ignoring it... Nov 28 16:07:16.380 INFO [stderr] --> src/encoder.rs:97:6 Nov 28 16:07:16.380 INFO [stderr] | Nov 28 16:07:16.380 INFO [stderr] 97 | //! [`Encodable::encode`] is called before returning an error; such callbacks should respond to Nov 28 16:07:16.380 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 16:07:16.380 INFO [stderr] | Nov 28 16:07:16.380 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 16:07:16.380 INFO [stderr] Nov 28 16:07:16.499 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 2.20s Nov 28 16:07:16.507 INFO [stderr] su: No module specific data is present Nov 28 16:07:16.835 INFO running `"docker" "inspect" "458eefd0a79bc9f04c6bf2743682c76f87aa7bd9839cb6da5d0d1986fc0cb9d8"` Nov 28 16:07:16.926 INFO running `"docker" "rm" "-f" "458eefd0a79bc9f04c6bf2743682c76f87aa7bd9839cb6da5d0d1986fc0cb9d8"` Nov 28 16:07:17.058 INFO [stdout] 458eefd0a79bc9f04c6bf2743682c76f87aa7bd9839cb6da5d0d1986fc0cb9d8