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