Dec 02 07:26:00.671 INFO documenting google-androidmanagement1-1.0.8+20181001 against master#147e60c5f89cfa2d3ffc247413956a37582c98e7 for pr-55318-1
Dec 02 07:26:00.671 INFO running `"docker" "create" "-v" "/mnt/big/crater/work/local/target-dirs/pr-55318-1/worker-7/master#147e60c5f89cfa2d3ffc247413956a37582c98e7:/target:rw,Z" "-v" "/mnt/big/crater/work/local/test-source/worker-7/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 07:26:00.868 INFO [stdout] 35f59caa4240be00767bc4ff03eaa20bd8bc85b88be01485127bc006e9330a9d
Dec 02 07:26:00.870 INFO running `"docker" "start" "-a" "35f59caa4240be00767bc4ff03eaa20bd8bc85b88be01485127bc006e9330a9d"`
Dec 02 07:26:01.411 INFO [stderr] usermod: no changes
Dec 02 07:26:01.619 INFO [stderr]  Documenting google-androidmanagement1 v1.0.8+20181001 (/source)
Dec 02 07:26:07.944 INFO [stderr] warning: `[2]` cannot be resolved, ignoring it...
Dec 02 07:26:07.944 INFO [stderr]    --> src/lib.rs:469:571
Dec 02 07:26:07.944 INFO [stderr]     |
Dec 02 07:26:07.944 INFO [stderr] 469 |     /// For settings with nested fields, if a particular nested field is out of compliance, this specifies the full path to the offending field. The path is formatted in the same way the policy JSON field would be referenced in JavaScript, that is: 1) For object-typed fields, the field name is followed by a dot then by a  subfield name. 2) For array-typed fields, the field name is followed by the array index  enclosed in brackets. For example, to indicate a problem with the url field in the externalData field in the 3rd application, the path would be applications[2].externalData.url
Dec 02 07:26:07.944 INFO [stderr]     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           ^ cannot be resolved, ignoring
Dec 02 07:26:07.944 INFO [stderr]     |
Dec 02 07:26:07.944 INFO [stderr]     = note: #[warn(intra_doc_link_resolution_failure)] on by default
Dec 02 07:26:07.944 INFO [stderr]     = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`
Dec 02 07:26:07.944 INFO [stderr] 
Dec 02 07:26:08.212 INFO [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.78s
Dec 02 07:26:08.228 INFO [stderr] su: No module specific data is present
Dec 02 07:26:08.509 INFO running `"docker" "inspect" "35f59caa4240be00767bc4ff03eaa20bd8bc85b88be01485127bc006e9330a9d"`
Dec 02 07:26:08.614 INFO running `"docker" "rm" "-f" "35f59caa4240be00767bc4ff03eaa20bd8bc85b88be01485127bc006e9330a9d"`
Dec 02 07:26:08.744 INFO [stdout] 35f59caa4240be00767bc4ff03eaa20bd8bc85b88be01485127bc006e9330a9d