Nov 28 15:08:30.376 INFO documenting ct-utils-0.0.1 against master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb for pr-55318 Nov 28 15:08:30.376 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-7/master#6bfb46e4ac9a2704f06de1a2ff7a4612cd70c8cb:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 15:08:30.818 INFO [stdout] 245dff973df62ef0200029007f6060118047a4116e0218dabf7e8efaee772ae3 Nov 28 15:08:30.820 INFO running `"docker" "start" "-a" "245dff973df62ef0200029007f6060118047a4116e0218dabf7e8efaee772ae3"` Nov 28 15:08:31.939 INFO [stderr] usermod: no changes Nov 28 15:08:31.996 INFO [stderr] Documenting ct-utils v0.0.1 (/source) Nov 28 15:08:33.727 INFO [stderr] warning: `[CTIf]` cannot be resolved, ignoring it... Nov 28 15:08:33.727 INFO [stderr] --> src/ct_if.rs:1:1 Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] 1 | / //! This module defines a types to encode an IF test within the type system. Nov 28 15:08:33.727 INFO [stderr] 2 | | //! Nov 28 15:08:33.727 INFO [stderr] 3 | | //! The idea behind this concept is to match the condition, which is a type, Nov 28 15:08:33.727 INFO [stderr] 4 | | //! with the structure the test is implemented for. Nov 28 15:08:33.727 INFO [stderr] ... | Nov 28 15:08:33.727 INFO [stderr] 36 | | //! made easy by utilizing the macro [`ctif_specialize`]. Nov 28 15:08:33.727 INFO [stderr] 37 | | //! Nov 28 15:08:33.727 INFO [stderr] | |___^ Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 15:08:33.727 INFO [stderr] = note: the link appears in this line: Nov 28 15:08:33.727 INFO [stderr] Nov 28 15:08:33.727 INFO [stderr] - If the receiving type parameter is constrained, the generic [`CTIf`] causes Nov 28 15:08:33.727 INFO [stderr] ^^^^^^ Nov 28 15:08:33.727 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.727 INFO [stderr] Nov 28 15:08:33.727 INFO [stderr] warning: `[CTIf]` cannot be resolved, ignoring it... Nov 28 15:08:33.727 INFO [stderr] --> src/ct_if.rs:1:1 Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] 1 | / //! This module defines a types to encode an IF test within the type system. Nov 28 15:08:33.727 INFO [stderr] 2 | | //! Nov 28 15:08:33.727 INFO [stderr] 3 | | //! The idea behind this concept is to match the condition, which is a type, Nov 28 15:08:33.727 INFO [stderr] 4 | | //! with the structure the test is implemented for. Nov 28 15:08:33.727 INFO [stderr] ... | Nov 28 15:08:33.727 INFO [stderr] 36 | | //! made easy by utilizing the macro [`ctif_specialize`]. Nov 28 15:08:33.727 INFO [stderr] 37 | | //! Nov 28 15:08:33.727 INFO [stderr] | |___^ Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] = note: the link appears in this line: Nov 28 15:08:33.727 INFO [stderr] Nov 28 15:08:33.727 INFO [stderr] You have to create your own specialized implementation of [`CTIf`], which is Nov 28 15:08:33.727 INFO [stderr] ^^^^^^ Nov 28 15:08:33.727 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.727 INFO [stderr] Nov 28 15:08:33.727 INFO [stderr] warning: `[CTCons]` cannot be resolved, ignoring it... Nov 28 15:08:33.727 INFO [stderr] --> src/ct_cons.rs:1:49 Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] 1 | //! This module defines a cons list for types, [`CTCons`]. Nov 28 15:08:33.727 INFO [stderr] | ^^^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.727 INFO [stderr] Nov 28 15:08:33.727 INFO [stderr] warning: `[CTSized]` cannot be resolved, ignoring it... Nov 28 15:08:33.727 INFO [stderr] --> src/ct_cons.rs:3:10 Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] 3 | //! See [`CTSized`] and [`CTOffset`] for more information about querying the cons list. Nov 28 15:08:33.727 INFO [stderr] | ^^^^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.727 INFO [stderr] Nov 28 15:08:33.727 INFO [stderr] warning: `[CTOffset]` cannot be resolved, ignoring it... Nov 28 15:08:33.727 INFO [stderr] --> src/ct_cons.rs:3:26 Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] 3 | //! See [`CTSized`] and [`CTOffset`] for more information about querying the cons list. Nov 28 15:08:33.727 INFO [stderr] | ^^^^^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.727 INFO [stderr] | Nov 28 15:08:33.727 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.727 INFO [stderr] Nov 28 15:08:33.737 INFO [stderr] warning: `[CTIf::Path]` cannot be resolved, ignoring it... Nov 28 15:08:33.737 INFO [stderr] --> src/ct_if.rs:157:12 Nov 28 15:08:33.737 INFO [stderr] | Nov 28 15:08:33.737 INFO [stderr] 157 | $( #[$meta_links] )* Nov 28 15:08:33.737 INFO [stderr] | ^^^^^^^^^^^^^^ Nov 28 15:08:33.737 INFO [stderr] | Nov 28 15:08:33.737 INFO [stderr] ::: src/ct_cons.rs:185:1 Nov 28 15:08:33.737 INFO [stderr] | Nov 28 15:08:33.737 INFO [stderr] 185 | / ctif_specialize!{ Nov 28 15:08:33.737 INFO [stderr] 186 | | /// Specialized implementation of [`IfCheck`] to accomodate for the additional constraints Nov 28 15:08:33.737 INFO [stderr] 187 | | /// necessary on [`CTIf::Path`]. Nov 28 15:08:33.737 INFO [stderr] 188 | | trait_name = CTIfOffset, Nov 28 15:08:33.737 INFO [stderr] 189 | | conditions = [Unsigned, Add] Nov 28 15:08:33.737 INFO [stderr] 190 | | } Nov 28 15:08:33.737 INFO [stderr] | |_- in this macro invocation Nov 28 15:08:33.737 INFO [stderr] | Nov 28 15:08:33.737 INFO [stderr] = note: the link appears in this line: Nov 28 15:08:33.737 INFO [stderr] Nov 28 15:08:33.737 INFO [stderr] necessary on [`CTIf::Path`]. Nov 28 15:08:33.737 INFO [stderr] ^^^^^^^^^^^^ Nov 28 15:08:33.737 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.737 INFO [stderr] Nov 28 15:08:33.737 INFO [stderr] warning: `[CTIf]` cannot be resolved, ignoring it... Nov 28 15:08:33.737 INFO [stderr] --> src/ct_if.rs:119:29 Nov 28 15:08:33.737 INFO [stderr] | Nov 28 15:08:33.737 INFO [stderr] 119 | /// Macro for specializing [`CTIf`]. Nov 28 15:08:33.737 INFO [stderr] | ^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.737 INFO [stderr] | Nov 28 15:08:33.737 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.737 INFO [stderr] Nov 28 15:08:33.737 INFO [stderr] warning: `[CTIf]` cannot be resolved, ignoring it... Nov 28 15:08:33.737 INFO [stderr] --> src/ct_if.rs:121:65 Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] 121 | /// If receiving associated types are constrained, the generic [`CTIf`] is not usable any more Nov 28 15:08:33.738 INFO [stderr] | ^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.738 INFO [stderr] Nov 28 15:08:33.738 INFO [stderr] warning: `[CTIf]` cannot be resolved, ignoring it... Nov 28 15:08:33.738 INFO [stderr] --> src/ct_if.rs:123:60 Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] 123 | /// Solving this requires building a new trait similar to [`CTIf`] with constraints which are Nov 28 15:08:33.738 INFO [stderr] | ^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.738 INFO [stderr] Nov 28 15:08:33.738 INFO [stderr] warning: `[CTIf::Path]` cannot be resolved, ignoring it... Nov 28 15:08:33.738 INFO [stderr] --> src/ct_if.rs:124:70 Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] 124 | /// specific to your use case. These constraints will be applied to [`CTIf::Path`]. Nov 28 15:08:33.738 INFO [stderr] | ^^^^^^^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.738 INFO [stderr] Nov 28 15:08:33.738 INFO [stderr] warning: `[IfCheck]` cannot be resolved, ignoring it... Nov 28 15:08:33.738 INFO [stderr] --> src/ct_if.rs:127:13 Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] 127 | /// it for [`IfCheck`], the latter can be re-used accross specializations. Nov 28 15:08:33.738 INFO [stderr] | ^^^^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.738 INFO [stderr] Nov 28 15:08:33.738 INFO [stderr] warning: `[CTIf]` cannot be resolved, ignoring it... Nov 28 15:08:33.738 INFO [stderr] --> src/ct_if.rs:131:56 Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] 131 | /// Using this specialized trait is analogue to using [`CTIf`] and [`IfCheck`]. Nov 28 15:08:33.738 INFO [stderr] | ^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.738 INFO [stderr] Nov 28 15:08:33.738 INFO [stderr] warning: `[IfCheck]` cannot be resolved, ignoring it... Nov 28 15:08:33.738 INFO [stderr] --> src/ct_if.rs:131:69 Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] 131 | /// Using this specialized trait is analogue to using [`CTIf`] and [`IfCheck`]. Nov 28 15:08:33.738 INFO [stderr] | ^^^^^^^^^ cannot be resolved, ignoring Nov 28 15:08:33.738 INFO [stderr] | Nov 28 15:08:33.738 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 15:08:33.738 INFO [stderr] Nov 28 15:08:33.836 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 1.88s Nov 28 15:08:33.838 INFO [stderr] su: No module specific data is present Nov 28 15:08:34.243 INFO running `"docker" "inspect" "245dff973df62ef0200029007f6060118047a4116e0218dabf7e8efaee772ae3"` Nov 28 15:08:34.369 INFO running `"docker" "rm" "-f" "245dff973df62ef0200029007f6060118047a4116e0218dabf7e8efaee772ae3"` Nov 28 15:08:34.506 INFO [stdout] 245dff973df62ef0200029007f6060118047a4116e0218dabf7e8efaee772ae3