Nov 28 07:55:54.584 INFO documenting trust-dns-resolver-0.10.0 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318 Nov 28 07:55:54.585 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-1/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-1/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 07:55:55.072 INFO [stdout] a8ea9119fa457fb1e1e7f083fdb3ed8e1432269588e40f9fb80f6abb1a879d7e Nov 28 07:55:55.078 INFO running `"docker" "start" "-a" "a8ea9119fa457fb1e1e7f083fdb3ed8e1432269588e40f9fb80f6abb1a879d7e"` Nov 28 07:55:56.331 INFO [stderr] usermod: no changes Nov 28 07:55:56.786 INFO [stderr] Checking hostname v0.1.5 Nov 28 07:55:56.787 INFO [stderr] Checking socket2 v0.3.8 Nov 28 07:55:57.351 INFO [stderr] Checking resolv-conf v0.6.1 Nov 28 07:55:57.990 INFO [stderr] Checking trust-dns-proto v0.5.0 Nov 28 07:56:02.546 INFO [stderr] Documenting trust-dns-resolver v0.10.0 (/source) Nov 28 07:56:08.063 INFO [stderr] warning: `[trust_dns_resolver::ResolverFuture]` cannot be resolved, ignoring it... Nov 28 07:56:08.064 INFO [stderr] --> src/resolver.rs:29:204 Nov 28 07:56:08.065 INFO [stderr] | Nov 28 07:56:08.065 INFO [stderr] 29 | /// Special note about resource consumption. The Resolver and all TRust-DNS software is built around the Tokio async-io library. This synchronous Resolver is intended to be a simpler wrapper for of the [`trust_dns_resolver::ResolverFuture`]. To allow the Resolver to be [`Send`] + [`Sync`], the construction of the `ResolverFuture` is lazy, this means some of the features of the `ResolverFuture`, like performance based resolution via the most efficient `NameServer` will be lost (the lookup cache is shared across invocations of the `Resolver`). If these other features of the TRust-DNS Resolver are desired, please use the tokio based `ResolverFuture`. Nov 28 07:56:08.067 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.068 INFO [stderr] | Nov 28 07:56:08.068 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 07:56:08.069 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.069 INFO [stderr] Nov 28 07:56:08.070 INFO [stderr] warning: `[AsyncResolver]` cannot be resolved, ignoring it... Nov 28 07:56:08.071 INFO [stderr] --> src/async_resolver/background.rs:29:6 Nov 28 07:56:08.071 INFO [stderr] | Nov 28 07:56:08.072 INFO [stderr] 29 | /// [`AsyncResolver`] handles linked to that background task. When all of its Nov 28 07:56:08.072 INFO [stderr] | ^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.073 INFO [stderr] | Nov 28 07:56:08.074 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.074 INFO [stderr] Nov 28 07:56:08.074 INFO [stderr] warning: `[AsyncResolver]` cannot be resolved, ignoring it... Nov 28 07:56:08.074 INFO [stderr] --> src/async_resolver/background.rs:30:6 Nov 28 07:56:08.074 INFO [stderr] | Nov 28 07:56:08.074 INFO [stderr] 30 | /// [`AsyncResolver`]s have been dropped, the background future will finish. Nov 28 07:56:08.074 INFO [stderr] | ^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.074 INFO [stderr] | Nov 28 07:56:08.074 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.074 INFO [stderr] Nov 28 07:56:08.074 INFO [stderr] warning: `[trust_dns_resolver::ResolverFuture]` cannot be resolved, ignoring it... Nov 28 07:56:08.074 INFO [stderr] --> src/resolver.rs:29:204 Nov 28 07:56:08.074 INFO [stderr] | Nov 28 07:56:08.074 INFO [stderr] 29 | /// Special note about resource consumption. The Resolver and all TRust-DNS software is built around the Tokio async-io library. This synchronous Resolver is intended to be a simpler wrapper for of the [`trust_dns_resolver::ResolverFuture`]. To allow the Resolver to be [`Send`] + [`Sync`], the construction of the `ResolverFuture` is lazy, this means some of the features of the `ResolverFuture`, like performance based resolution via the most efficient `NameServer` will be lost (the lookup cache is shared across invocations of the `Resolver`). If these other features of the TRust-DNS Resolver are desired, please use the tokio based `ResolverFuture`. Nov 28 07:56:08.074 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.074 INFO [stderr] | Nov 28 07:56:08.074 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.074 INFO [stderr] Nov 28 07:56:08.074 INFO [stderr] warning: `[ResolverConfig::default]` cannot be resolved, ignoring it... Nov 28 07:56:08.083 INFO [stderr] --> src/resolver.rs:94:14 Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] 94 | /// See [`ResolverConfig::default`] and [`ResolverOpts::default`] for more information. Nov 28 07:56:08.083 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.083 INFO [stderr] Nov 28 07:56:08.083 INFO [stderr] warning: `[ResolverOpts::default]` cannot be resolved, ignoring it... Nov 28 07:56:08.083 INFO [stderr] --> src/resolver.rs:94:46 Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] 94 | /// See [`ResolverConfig::default`] and [`ResolverOpts::default`] for more information. Nov 28 07:56:08.083 INFO [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.083 INFO [stderr] Nov 28 07:56:08.083 INFO [stderr] warning: `[Self::lookup_ip]` cannot be resolved, ignoring it... Nov 28 07:56:08.083 INFO [stderr] --> src/resolver.rs:126:72 Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] 126 | /// *WARNING* This interface may change in the future, please use [`Self::lookup_ip`] or another variant for more stable interfaces. Nov 28 07:56:08.083 INFO [stderr] | ^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.083 INFO [stderr] Nov 28 07:56:08.083 INFO [stderr] warning: `[from_ascii]` cannot be resolved, ignoring it... Nov 28 07:56:08.083 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/trust-dns-proto-0.5.0/src/rr/domain/name.rs:1101:66 Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] 1101 | /// Uses the Name::from_utf8 conversion on this string, see [`from_ascii`] for ascii only, or for preserving case Nov 28 07:56:08.083 INFO [stderr] | ^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.083 INFO [stderr] Nov 28 07:56:08.083 INFO [stderr] warning: `[Record]` cannot be resolved, ignoring it... Nov 28 07:56:08.083 INFO [stderr] --> /cargo-home/registry/src/github.com-1ecc6299db9ec823/trust-dns-proto-0.5.0/src/op/message.rs:663:67 Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] 663 | /// The message taken in should be processed and then return [`Record`]s which should be Nov 28 07:56:08.083 INFO [stderr] | ^^^^^^^^ cannot be resolved, ignoring Nov 28 07:56:08.083 INFO [stderr] | Nov 28 07:56:08.083 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 07:56:08.083 INFO [stderr] Nov 28 07:56:08.436 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 12.07s Nov 28 07:56:08.467 INFO [stderr] su: No module specific data is present Nov 28 07:56:09.477 INFO running `"docker" "inspect" "a8ea9119fa457fb1e1e7f083fdb3ed8e1432269588e40f9fb80f6abb1a879d7e"` Nov 28 07:56:09.685 INFO running `"docker" "rm" "-f" "a8ea9119fa457fb1e1e7f083fdb3ed8e1432269588e40f9fb80f6abb1a879d7e"` Nov 28 07:56:09.859 INFO [stdout] a8ea9119fa457fb1e1e7f083fdb3ed8e1432269588e40f9fb80f6abb1a879d7e