[INFO] fetching crate mz_rusoto_iot 0.46.0...
[INFO] documenting mz_rusoto_iot-0.46.0 against 1.69.0 for beta-1.70-rustdoc-1
[INFO] extracting crate mz_rusoto_iot 0.46.0 into /workspace/builds/worker-6-tc1/source
[INFO] validating manifest of crates.io crate mz_rusoto_iot 0.46.0 on toolchain 1.69.0
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.69.0" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking crates.io crate mz_rusoto_iot 0.46.0
[INFO] finished tweaking crates.io crate mz_rusoto_iot 0.46.0
[INFO] tweaked toml for crates.io crate mz_rusoto_iot 0.46.0 written to /workspace/builds/worker-6-tc1/source/Cargo.toml
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" __CARGO_TEST_CHANNEL_OVERRIDE_DO_NOT_USE_THIS="nightly" "/workspace/cargo-home/bin/cargo" "+1.69.0" "generate-lockfile" "--manifest-path" "Cargo.toml" "-Zno-index-update", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.69.0" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:5ff2268d62e97bff2cde7d5815dd6ed5b47097566f13b8d0ca110b04b60e07ed" "/opt/rustwide/cargo-home/bin/cargo" "+1.69.0" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 0c51f96bbb5eece868bbc6257c00a4bf4ea885ebbbd20d4cb4b306d5224a6e83
[INFO] running `Command { std: "docker" "start" "-a" "0c51f96bbb5eece868bbc6257c00a4bf4ea885ebbbd20d4cb4b306d5224a6e83", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "0c51f96bbb5eece868bbc6257c00a4bf4ea885ebbbd20d4cb4b306d5224a6e83", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "0c51f96bbb5eece868bbc6257c00a4bf4ea885ebbbd20d4cb4b306d5224a6e83", kill_on_drop: false }`
[INFO] [stdout] 0c51f96bbb5eece868bbc6257c00a4bf4ea885ebbbd20d4cb4b306d5224a6e83
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:5ff2268d62e97bff2cde7d5815dd6ed5b47097566f13b8d0ca110b04b60e07ed" "/opt/rustwide/cargo-home/bin/cargo" "+1.69.0" "doc" "--frozen" "--no-deps" "--document-private-items" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 9372fc7ee8cd3ae48e4beef1b862257278bad506d8be5012c052ccb148408e55
[INFO] running `Command { std: "docker" "start" "-a" "9372fc7ee8cd3ae48e4beef1b862257278bad506d8be5012c052ccb148408e55", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.56
[INFO] [stderr]    Compiling libc v0.2.142
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling openssl-sys v0.9.87
[INFO] [stderr]    Compiling thiserror v1.0.40
[INFO] [stderr]    Compiling ucd-trie v0.1.5
[INFO] [stderr]    Compiling openssl v0.10.52
[INFO] [stderr]     Checking http-body v0.3.1
[INFO] [stderr]    Compiling native-tls v0.2.11
[INFO] [stderr]     Checking digest v0.9.0
[INFO] [stderr]     Checking iana-time-zone v0.1.56
[INFO] [stderr]     Checking subtle v2.4.1
[INFO] [stderr]     Checking block-buffer v0.9.0
[INFO] [stderr]     Checking zeroize v1.6.0
[INFO] [stderr]     Checking shlex v0.1.1
[INFO] [stderr]     Checking crypto-mac v0.10.1
[INFO] [stderr]     Checking sha2 v0.9.9
[INFO] [stderr]     Checking hmac v0.10.1
[INFO] [stderr]     Checking md5 v0.7.0
[INFO] [stderr]     Checking xml-rs v0.8.4
[INFO] [stderr]    Compiling quote v1.0.26
[INFO] [stderr]    Compiling syn v2.0.15
[INFO] [stderr]     Checking iovec v0.1.4
[INFO] [stderr]     Checking net2 v0.2.38
[INFO] [stderr]     Checking signal-hook-registry v1.4.1
[INFO] [stderr]     Checking socket2 v0.3.19
[INFO] [stderr]     Checking dirs-sys-next v0.1.2
[INFO] [stderr]     Checking time v0.1.45
[INFO] [stderr]     Checking dirs-next v2.0.0
[INFO] [stderr]     Checking mio v0.6.23
[INFO] [stderr]     Checking mio-uds v0.6.8
[INFO] [stderr]    Compiling futures-macro v0.3.28
[INFO] [stderr]    Compiling thiserror-impl v1.0.40
[INFO] [stderr]    Compiling serde_derive v1.0.160
[INFO] [stderr]    Compiling openssl-macros v0.1.1
[INFO] [stderr]    Compiling async-trait v0.1.68
[INFO] [stderr]     Checking futures-util v0.3.28
[INFO] [stderr]    Compiling tokio-macros v0.2.6
[INFO] [stderr]    Compiling pin-project-internal v1.0.12
[INFO] [stderr]    Compiling time-macros-impl v0.1.2
[INFO] [stderr]    Compiling pest v2.6.0
[INFO] [stderr]     Checking tokio v0.2.25
[INFO] [stderr]     Checking time-macros v0.1.1
[INFO] [stderr]     Checking time v0.2.27
[INFO] [stderr]     Checking pin-project v1.0.12
[INFO] [stderr]     Checking tracing-futures v0.2.5
[INFO] [stderr]    Compiling semver-parser v0.10.2
[INFO] [stderr]    Compiling semver v0.11.0
[INFO] [stderr]     Checking serde v1.0.160
[INFO] [stderr]    Compiling rustc_version v0.3.3
[INFO] [stderr]    Compiling mz_rusoto_core v0.46.0
[INFO] [stderr]     Checking futures-executor v0.3.28
[INFO] [stderr]     Checking futures v0.3.28
[INFO] [stderr]     Checking tokio-util v0.3.1
[INFO] [stderr]     Checking tokio-tls v0.3.1
[INFO] [stderr]     Checking h2 v0.2.7
[INFO] [stderr]     Checking serde_json v1.0.96
[INFO] [stderr]     Checking chrono v0.4.24
[INFO] [stderr]     Checking hyper v0.13.10
[INFO] [stderr]     Checking mz_rusoto_credential v0.46.0
[INFO] [stderr]     Checking hyper-tls v0.4.3
[INFO] [stderr]     Checking mz_rusoto_signature v0.46.0
[INFO] [stderr]  Documenting mz_rusoto_iot v0.46.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2332:85
[INFO] [stdout]      |
[INFO] [stdout] 2332 |     /// <p><p>(Optional) When true, you can delete a job execution which is &quot;IN<em>PROGRESS&quot;. Otherwise, you can only delete a ...
[INFO] [stdout]      |                                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: `#[warn(rustdoc::invalid_html_tags)]` on by default
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2332 |     /// <p><p>(Optional) When true, you can delete a job execution which is &quot;`IN<em>`PROGRESS&quot;. Otherwise, you can only delete a job execution which is in a terminal state (&quot;SUCCEEDED&quot;, &quot;FAILED&quot;, &quot;REJECTED&quot;, &quot;REMOVED&quot; or &quot;CANCELED&quot;) or an exception will occur. The default is false.</p> <note> <p>Deleting a job execution which is &quot;IN</em>PROGRESS&quot;, will cause the device to be unable to access job information or update the job execution status. Use caution and ensure that the device is able to recover to a valid state.</p> </note></p>
[INFO] [stdout]      |                                                                                   +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2332:398
[INFO] [stdout]      |
[INFO] [stdout] 2332 | ... false.</p> <note> <p>Deleting a job execution which is &quot;IN</em>PROGRESS&quot;, will cause the device to be unable to access job ...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2347:75
[INFO] [stdout]      |
[INFO] [stdout] 2347 |     /// <p><p>(Optional) When true, you can delete a job which is &quot;IN<em>PROGRESS&quot;. Otherwise, you can only delete a job which ...
[INFO] [stdout]      |                                                                           ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2347 |     /// <p><p>(Optional) When true, you can delete a job which is &quot;`IN<em>`PROGRESS&quot;. Otherwise, you can only delete a job which is in a terminal state (&quot;COMPLETED&quot; or &quot;CANCELED&quot;) or an exception will occur. The default is false.</p> <note> <p>Deleting a job which is &quot;IN</em>PROGRESS&quot;, will cause a device which is executing the job to be unable to access job information or update the job execution status. Use caution and ensure that each device executing a job which is deleted is able to recover to a valid state.</p> </note></p>
[INFO] [stdout]      |                                                                         +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2347:305
[INFO] [stdout]      |
[INFO] [stdout] 2347 | ...default is false.</p> <note> <p>Deleting a job which is &quot;IN</em>PROGRESS&quot;, will cause a device which is executing the job to...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2978:325
[INFO] [stdout]      |
[INFO] [stdout] 2978 | ...d shadow data.</p> </li> <li> <p>REGISTRY<em>AND</em>CONNECTIVITY<em>STATUS - Your thing index contains registry data and thing connec...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2978 |     /// <p><p>Contains a value that specifies the type of indexing performed. Valid values are:</p> <ul> <li> <p>REGISTRY – Your thing index contains only registry data.</p> </li> <li> <p>REGISTRY<em>AND</em>SHADOW - Your thing index contains registry data and shadow data.</p> </li> <li> <p>REGISTRY<em>AND</em>`CONNECTIVITY<em>`STATUS - Your thing index contains registry data and thing connectivity status data.</p> </li> <li> <p>REGISTRY</em>AND<em>SHADOW</em>AND<em>CONNECTIVITY</em>STATUS - Your thing index contains registry data, shadow data, and thing connectivity status data.</p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                         +                +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2978:440
[INFO] [stdout]      |
[INFO] [stdout] 2978 | ...a and thing connectivity status data.</p> </li> <li> <p>REGISTRY</em>AND<em>SHADOW</em>AND<em>CONNECTIVITY</em>STATUS - Your thing ind...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:7977:90
[INFO] [stdout]      |
[INFO] [stdout] 7977 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>IN<em>PROGRESS</dt> <dd> <p>A topic rule destinati...
[INFO] [stdout]      |                                                                                          ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 7977 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>`IN<em>`PROGRESS</dt> <dd> <p>A topic rule destination was created but has not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> <dt>ENABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is allowed. You can set <code>status</code> to <code>DISABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>DISABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is not allowed. You can set <code>status</code> to <code>ENABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>ERROR</dt> <dd> <p>Confirmation could not be completed, for example if the confirmation timed out. You can call <code>GetTopicRuleDestination</code> for details about the error. You can set <code>status</code> to <code>IN_PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                        +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:7977:224
[INFO] [stdout]      |
[INFO] [stdout] 7977 | ... not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8009:90
[INFO] [stdout]      |
[INFO] [stdout] 8009 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>IN<em>PROGRESS</dt> <dd> <p>A topic rule destinati...
[INFO] [stdout]      |                                                                                          ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 8009 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>`IN<em>`PROGRESS</dt> <dd> <p>A topic rule destination was created but has not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> <dt>ENABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is allowed. You can set <code>status</code> to <code>DISABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>DISABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is not allowed. You can set <code>status</code> to <code>ENABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>ERROR</dt> <dd> <p>Confirmation could not be completed, for example if the confirmation timed out. You can call <code>GetTopicRuleDestination</code> for details about the error. You can set <code>status</code> to <code>IN_PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                        +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8009:224
[INFO] [stdout]      |
[INFO] [stdout] 8009 | ... not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8778:90
[INFO] [stdout]      |
[INFO] [stdout] 8778 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>IN<em>PROGRESS</dt> <dd> <p>A topic rule destinati...
[INFO] [stdout]      |                                                                                          ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 8778 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>`IN<em>`PROGRESS</dt> <dd> <p>A topic rule destination was created but has not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> <dt>ENABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is allowed. You can set <code>status</code> to <code>DISABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>DISABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is not allowed. You can set <code>status</code> to <code>ENABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>ERROR</dt> <dd> <p>Confirmation could not be completed, for example if the confirmation timed out. You can call <code>GetTopicRuleDestination</code> for details about the error. You can set <code>status</code> to <code>IN_PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                        +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8778:224
[INFO] [stdout]      |
[INFO] [stdout] 8778 | ... not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 12 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 44.94s
[INFO] running `Command { std: "docker" "inspect" "9372fc7ee8cd3ae48e4beef1b862257278bad506d8be5012c052ccb148408e55", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "9372fc7ee8cd3ae48e4beef1b862257278bad506d8be5012c052ccb148408e55", kill_on_drop: false }`
[INFO] [stdout] 9372fc7ee8cd3ae48e4beef1b862257278bad506d8be5012c052ccb148408e55
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "DOCS_RS=1" "-e" "RUSTC_BOOTSTRAP=1" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:5ff2268d62e97bff2cde7d5815dd6ed5b47097566f13b8d0ca110b04b60e07ed" "/opt/rustwide/cargo-home/bin/cargo" "+1.69.0" "rustdoc" "--lib" "-Zrustdoc-map" "-Z" "unstable-options" "--config" "build.rustdocflags=[\"-Z\", \"unstable-options\", \"--document-private-items\"]" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 95390c774ec12011dcfcc389d75709703366601bab496cc67631be030c9cca1e
[INFO] running `Command { std: "docker" "start" "-a" "95390c774ec12011dcfcc389d75709703366601bab496cc67631be030c9cca1e", kill_on_drop: false }`
[INFO] [stderr]     Blocking waiting for file lock on package cache
[INFO] [stderr]  Documenting mz_rusoto_iot v0.46.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2332:85
[INFO] [stdout]      |
[INFO] [stdout] 2332 |     /// <p><p>(Optional) When true, you can delete a job execution which is &quot;IN<em>PROGRESS&quot;. Otherwise, you can only delete a ...
[INFO] [stdout]      |                                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout]      = note: `#[warn(rustdoc::invalid_html_tags)]` on by default
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2332 |     /// <p><p>(Optional) When true, you can delete a job execution which is &quot;`IN<em>`PROGRESS&quot;. Otherwise, you can only delete a job execution which is in a terminal state (&quot;SUCCEEDED&quot;, &quot;FAILED&quot;, &quot;REJECTED&quot;, &quot;REMOVED&quot; or &quot;CANCELED&quot;) or an exception will occur. The default is false.</p> <note> <p>Deleting a job execution which is &quot;IN</em>PROGRESS&quot;, will cause the device to be unable to access job information or update the job execution status. Use caution and ensure that the device is able to recover to a valid state.</p> </note></p>
[INFO] [stdout]      |                                                                                   +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2332:398
[INFO] [stdout]      |
[INFO] [stdout] 2332 | ... false.</p> <note> <p>Deleting a job execution which is &quot;IN</em>PROGRESS&quot;, will cause the device to be unable to access job ...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2347:75
[INFO] [stdout]      |
[INFO] [stdout] 2347 |     /// <p><p>(Optional) When true, you can delete a job which is &quot;IN<em>PROGRESS&quot;. Otherwise, you can only delete a job which ...
[INFO] [stdout]      |                                                                           ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2347 |     /// <p><p>(Optional) When true, you can delete a job which is &quot;`IN<em>`PROGRESS&quot;. Otherwise, you can only delete a job which is in a terminal state (&quot;COMPLETED&quot; or &quot;CANCELED&quot;) or an exception will occur. The default is false.</p> <note> <p>Deleting a job which is &quot;IN</em>PROGRESS&quot;, will cause a device which is executing the job to be unable to access job information or update the job execution status. Use caution and ensure that each device executing a job which is deleted is able to recover to a valid state.</p> </note></p>
[INFO] [stdout]      |                                                                         +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2347:305
[INFO] [stdout]      |
[INFO] [stdout] 2347 | ...default is false.</p> <note> <p>Deleting a job which is &quot;IN</em>PROGRESS&quot;, will cause a device which is executing the job to...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2978:325
[INFO] [stdout]      |
[INFO] [stdout] 2978 | ...d shadow data.</p> </li> <li> <p>REGISTRY<em>AND</em>CONNECTIVITY<em>STATUS - Your thing index contains registry data and thing connec...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2978 |     /// <p><p>Contains a value that specifies the type of indexing performed. Valid values are:</p> <ul> <li> <p>REGISTRY – Your thing index contains only registry data.</p> </li> <li> <p>REGISTRY<em>AND</em>SHADOW - Your thing index contains registry data and shadow data.</p> </li> <li> <p>REGISTRY<em>AND</em>`CONNECTIVITY<em>`STATUS - Your thing index contains registry data and thing connectivity status data.</p> </li> <li> <p>REGISTRY</em>AND<em>SHADOW</em>AND<em>CONNECTIVITY</em>STATUS - Your thing index contains registry data, shadow data, and thing connectivity status data.</p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                         +                +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2978:440
[INFO] [stdout]      |
[INFO] [stdout] 2978 | ...a and thing connectivity status data.</p> </li> <li> <p>REGISTRY</em>AND<em>SHADOW</em>AND<em>CONNECTIVITY</em>STATUS - Your thing ind...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:7977:90
[INFO] [stdout]      |
[INFO] [stdout] 7977 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>IN<em>PROGRESS</dt> <dd> <p>A topic rule destinati...
[INFO] [stdout]      |                                                                                          ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 7977 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>`IN<em>`PROGRESS</dt> <dd> <p>A topic rule destination was created but has not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> <dt>ENABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is allowed. You can set <code>status</code> to <code>DISABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>DISABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is not allowed. You can set <code>status</code> to <code>ENABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>ERROR</dt> <dd> <p>Confirmation could not be completed, for example if the confirmation timed out. You can call <code>GetTopicRuleDestination</code> for details about the error. You can set <code>status</code> to <code>IN_PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                        +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:7977:224
[INFO] [stdout]      |
[INFO] [stdout] 7977 | ... not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8009:90
[INFO] [stdout]      |
[INFO] [stdout] 8009 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>IN<em>PROGRESS</dt> <dd> <p>A topic rule destinati...
[INFO] [stdout]      |                                                                                          ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 8009 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>`IN<em>`PROGRESS</dt> <dd> <p>A topic rule destination was created but has not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> <dt>ENABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is allowed. You can set <code>status</code> to <code>DISABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>DISABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is not allowed. You can set <code>status</code> to <code>ENABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>ERROR</dt> <dd> <p>Confirmation could not be completed, for example if the confirmation timed out. You can call <code>GetTopicRuleDestination</code> for details about the error. You can set <code>status</code> to <code>IN_PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                        +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8009:224
[INFO] [stdout]      |
[INFO] [stdout] 8009 | ... not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8778:90
[INFO] [stdout]      |
[INFO] [stdout] 8778 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>IN<em>PROGRESS</dt> <dd> <p>A topic rule destinati...
[INFO] [stdout]      |                                                                                          ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 8778 |     /// <p><p>The status of the topic rule destination. Valid values are:</p> <dl> <dt>`IN<em>`PROGRESS</dt> <dd> <p>A topic rule destination was created but has not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> <dt>ENABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is allowed. You can set <code>status</code> to <code>DISABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>DISABLED</dt> <dd> <p>Confirmation was completed, and traffic to this destination is not allowed. You can set <code>status</code> to <code>ENABLED</code> by calling <code>UpdateTopicRuleDestination</code>.</p> </dd> <dt>ERROR</dt> <dd> <p>Confirmation could not be completed, for example if the confirmation timed out. You can call <code>GetTopicRuleDestination</code> for details about the error. You can set <code>status</code> to <code>IN_PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code>. Calling <code>UpdateTopicRuleDestination</code> causes a new confirmation challenge to be sent to your confirmation endpoint.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                        +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:8778:224
[INFO] [stdout]      |
[INFO] [stdout] 8778 | ... not been confirmed. You can set <code>status</code> to <code>IN</em>PROGRESS</code> by calling <code>UpdateTopicRuleDestination</code...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 12 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 6.07s
[INFO] running `Command { std: "docker" "inspect" "95390c774ec12011dcfcc389d75709703366601bab496cc67631be030c9cca1e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "95390c774ec12011dcfcc389d75709703366601bab496cc67631be030c9cca1e", kill_on_drop: false }`
[INFO] [stdout] 95390c774ec12011dcfcc389d75709703366601bab496cc67631be030c9cca1e
