Nov 28 13:45:09.519 INFO documenting google-dfareporting2d5-1.0.6+20170428 against try#f5a0bd723553ea4b7556bd7087b9f0919cafb483 for pr-55318 Nov 28 13:45:09.519 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318/worker-0/try#f5a0bd723553ea4b7556bd7087b9f0919cafb483:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-0/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 13:45:09.729 INFO [stdout] d503cd462fd1ed250070b6f3b095dc0685c8354ae01fbdefe8ecb26f9ee0f3de Nov 28 13:45:09.731 INFO running `"docker" "start" "-a" "d503cd462fd1ed250070b6f3b095dc0685c8354ae01fbdefe8ecb26f9ee0f3de"` Nov 28 13:45:10.290 INFO [stderr] usermod: no changes Nov 28 13:45:10.551 INFO [stderr] Documenting google-dfareporting2d5 v1.0.6+20170428 (/source) Nov 28 13:45:25.203 INFO [stderr] warning: `[]` cannot be resolved, ignoring it... Nov 28 13:45:25.203 INFO [stderr] --> src/lib.rs:711:160 Nov 28 13:45:25.203 INFO [stderr] | Nov 28 13:45:25.203 INFO [stderr] 711 | /// The alphanumeric encrypted user ID. When set, encryptionInfo should also be specified. This field is mutually exclusive with encryptedUserIdCandidates[] and mobileDeviceId. This or encryptedUserIdCandidates[] or mobileDeviceId is a required field. Nov 28 13:45:25.203 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 13:45:25.203 INFO [stderr] | Nov 28 13:45:25.203 INFO [stderr] = note: #[warn(intra_doc_link_resolution_failure)] on by default Nov 28 13:45:25.203 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:45:25.203 INFO [stderr] Nov 28 13:45:25.203 INFO [stderr] warning: `[]` cannot be resolved, ignoring it... Nov 28 13:45:25.204 INFO [stderr] --> src/lib.rs:711:216 Nov 28 13:45:25.204 INFO [stderr] | Nov 28 13:45:25.204 INFO [stderr] 711 | /// The alphanumeric encrypted user ID. When set, encryptionInfo should also be specified. This field is mutually exclusive with encryptedUserIdCandidates[] and mobileDeviceId. This or encryptedUserIdCandidates[] or mobileDeviceId is a required field. Nov 28 13:45:25.204 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 13:45:25.204 INFO [stderr] | Nov 28 13:45:25.207 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:45:25.207 INFO [stderr] Nov 28 13:45:25.207 INFO [stderr] warning: `[]` cannot be resolved, ignoring it... Nov 28 13:45:25.207 INFO [stderr] --> src/lib.rs:720:115 Nov 28 13:45:25.207 INFO [stderr] | Nov 28 13:45:25.207 INFO [stderr] 720 | /// The mobile device ID. This field is mutually exclusive with encryptedUserId and encryptedUserIdCandidates[]. This or encryptedUserId or encryptedUserIdCandidates[] is a required field. Nov 28 13:45:25.207 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 13:45:25.207 INFO [stderr] | Nov 28 13:45:25.207 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:45:25.207 INFO [stderr] Nov 28 13:45:25.207 INFO [stderr] warning: `[]` cannot be resolved, ignoring it... Nov 28 13:45:25.207 INFO [stderr] --> src/lib.rs:720:171 Nov 28 13:45:25.207 INFO [stderr] | Nov 28 13:45:25.207 INFO [stderr] 720 | /// The mobile device ID. This field is mutually exclusive with encryptedUserId and encryptedUserIdCandidates[]. This or encryptedUserId or encryptedUserIdCandidates[] is a required field. Nov 28 13:45:25.207 INFO [stderr] | ^ cannot be resolved, ignoring Nov 28 13:45:25.207 INFO [stderr] | Nov 28 13:45:25.207 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:45:25.207 INFO [stderr] Nov 28 13:45:25.207 INFO [stderr] warning: `[_]` cannot be resolved, ignoring it... Nov 28 13:45:25.207 INFO [stderr] --> src/lib.rs:1760:310 Nov 28 13:45:25.207 INFO [stderr] | Nov 28 13:45:25.207 INFO [stderr] 1760 | /// Value of the type= parameter in the floodlight tag, which the ad servers use to identify the activity group that the activity belongs to. This is optional: if empty, a new tag string will be generated for you. This string must be 1 to 8 characters long, with valid characters being [a-z][A-Z][0-9][-][ _ ]. This tag string must also be unique among activity groups of the same floodlight configuration. This field is read-only after insertion. Nov 28 13:45:25.207 INFO [stderr] | ^^^ cannot be resolved, ignoring Nov 28 13:45:25.207 INFO [stderr] | Nov 28 13:45:25.207 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:45:25.207 INFO [stderr] Nov 28 13:45:25.212 INFO [stderr] warning: `[_]` cannot be resolved, ignoring it... Nov 28 13:45:25.212 INFO [stderr] --> src/lib.rs:4901:273 Nov 28 13:45:25.212 INFO [stderr] | Nov 28 13:45:25.212 INFO [stderr] 4901 | /// Value of the cat= paramter in the floodlight tag, which the ad servers use to identify the activity. This is optional: if empty, a new tag string will be generated for you. This string must be 1 to 8 characters long, with valid characters being [a-z][A-Z][0-9][-][ _ ]. This tag string must also be unique among activities of the same activity group. This field is read-only after insertion. Nov 28 13:45:25.212 INFO [stderr] | ^^^ cannot be resolved, ignoring Nov 28 13:45:25.212 INFO [stderr] | Nov 28 13:45:25.212 INFO [stderr] = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]` Nov 28 13:45:25.212 INFO [stderr] Nov 28 13:45:26.561 INFO [stderr] Finished dev [unoptimized + debuginfo] target(s) in 16.24s Nov 28 13:45:26.580 INFO [stderr] su: No module specific data is present Nov 28 13:45:26.907 INFO running `"docker" "inspect" "d503cd462fd1ed250070b6f3b095dc0685c8354ae01fbdefe8ecb26f9ee0f3de"` Nov 28 13:45:27.057 INFO running `"docker" "rm" "-f" "d503cd462fd1ed250070b6f3b095dc0685c8354ae01fbdefe8ecb26f9ee0f3de"` Nov 28 13:45:27.191 INFO [stdout] d503cd462fd1ed250070b6f3b095dc0685c8354ae01fbdefe8ecb26f9ee0f3de