[INFO] fetching crate rusoto_ecs 0.48.0...
[INFO] documenting rusoto_ecs-0.48.0 against 1.69.0 for beta-1.70-rustdoc-1
[INFO] extracting crate rusoto_ecs 0.48.0 into /workspace/builds/worker-7-tc1/source
[INFO] validating manifest of crates.io crate rusoto_ecs 0.48.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 rusoto_ecs 0.48.0
[INFO] finished tweaking crates.io crate rusoto_ecs 0.48.0
[INFO] tweaked toml for crates.io crate rusoto_ecs 0.48.0 written to /workspace/builds/worker-7-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-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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] e20cbee720ace0ac402896bed5213d8af224e74c29eb958ac4c418dddebe8a98
[INFO] running `Command { std: "docker" "start" "-a" "e20cbee720ace0ac402896bed5213d8af224e74c29eb958ac4c418dddebe8a98", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "e20cbee720ace0ac402896bed5213d8af224e74c29eb958ac4c418dddebe8a98", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "e20cbee720ace0ac402896bed5213d8af224e74c29eb958ac4c418dddebe8a98", kill_on_drop: false }`
[INFO] [stdout] e20cbee720ace0ac402896bed5213d8af224e74c29eb958ac4c418dddebe8a98
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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] 8311154f6911babca4a87d0f14c27a60d8c143ffec4153cda3171ca81a6096fb
[INFO] running `Command { std: "docker" "start" "-a" "8311154f6911babca4a87d0f14c27a60d8c143ffec4153cda3171ca81a6096fb", kill_on_drop: false }`
[INFO] [stderr]    Compiling tokio v1.28.0
[INFO] [stderr]     Checking signal-hook-registry v1.4.1
[INFO] [stderr]     Checking socket2 v0.4.9
[INFO] [stderr]     Checking mio v0.8.6
[INFO] [stderr]     Checking generic-array v0.14.7
[INFO] [stderr]    Compiling tokio-macros v2.1.0
[INFO] [stderr]    Compiling openssl-macros v0.1.1
[INFO] [stderr]     Checking futures-util v0.3.28
[INFO] [stderr]     Checking serde v1.0.160
[INFO] [stderr]     Checking dirs-sys-next v0.1.2
[INFO] [stderr]     Checking shlex v1.1.0
[INFO] [stderr]     Checking zeroize v1.6.0
[INFO] [stderr]    Compiling rusoto_core v0.48.0
[INFO] [stderr]     Checking hex v0.4.3
[INFO] [stderr]     Checking dirs-next v2.0.0
[INFO] [stderr]     Checking digest v0.9.0
[INFO] [stderr]     Checking block-buffer v0.9.0
[INFO] [stderr]     Checking crypto-mac v0.11.1
[INFO] [stderr]     Checking md-5 v0.9.1
[INFO] [stderr]     Checking sha2 v0.9.9
[INFO] [stderr]     Checking hmac v0.11.0
[INFO] [stderr]     Checking openssl v0.10.52
[INFO] [stderr]     Checking futures-executor v0.3.28
[INFO] [stderr]     Checking chrono v0.4.24
[INFO] [stderr]     Checking serde_json v1.0.96
[INFO] [stderr]     Checking futures v0.3.28
[INFO] [stderr]     Checking native-tls v0.2.11
[INFO] [stderr]     Checking tokio-util v0.7.8
[INFO] [stderr]     Checking tokio-native-tls v0.3.1
[INFO] [stderr]     Checking h2 v0.3.18
[INFO] [stderr]     Checking hyper v0.14.26
[INFO] [stderr]     Checking rusoto_credential v0.48.0
[INFO] [stderr]     Checking hyper-tls v0.5.0
[INFO] [stderr]     Checking rusoto_signature v0.48.0
[INFO] [stderr]  Documenting rusoto_ecs v0.48.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:177:250
[INFO] [stdout]     |
[INFO] [stdout] 177 | ...provider is in the process of being deleted.</p> </dd> <dt>DELETE<em>COMPLETE</dt> <dd> <p>The capacity provider has been successfully...
[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] 177 |     /// <p><p>The update status of the capacity provider. The following are the possible states that will be returned.</p> <dl> <dt>DELETE<em>IN</em>PROGRESS</dt> <dd> <p>The capacity provider is in the process of being deleted.</p> </dd> <dt>`DELETE<em>`COMPLETE</dt> <dd> <p>The capacity provider has been successfully deleted and will have an <code>INACTIVE</code> status.</p> </dd> <dt>DELETE</em>FAILED</dt> <dd> <p>The capacity provider was unable to be deleted. The update status reason will provide further details about why the delete failed.</p> </dd> </dl></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                    +          +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:177:395
[INFO] [stdout]     |
[INFO] [stdout] 177 | ... will have an <code>INACTIVE</code> status.</p> </dd> <dt>DELETE</em>FAILED</dt> <dd> <p>The capacity provider was unable to be delete...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:215:342
[INFO] [stdout]     |
[INFO] [stdout] 215 | ...ling plan is provisioning or deprovisioning.</p> </dd> <dt>UPDATE<em>COMPLETE</dt> <dd> <p>The capacity providers have successfully up...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 215 |     /// <p><p>The status of the capacity providers associated with the cluster. The following are the states that will be returned:</p> <dl> <dt>UPDATE<em>IN</em>PROGRESS</dt> <dd> <p>The available capacity providers for the cluster are updating. This occurs when the Auto Scaling plan is provisioning or deprovisioning.</p> </dd> <dt>`UPDATE<em>`COMPLETE</dt> <dd> <p>The capacity providers have successfully updated.</p> </dd> <dt>UPDATE</em>FAILED</dt> <dd> <p>The capacity provider updates failed.</p> </dd> </dl></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                +          +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:215:438
[INFO] [stdout]     |
[INFO] [stdout] 215 | ...pacity providers have successfully updated.</p> </dd> <dt>UPDATE</em>FAILED</dt> <dd> <p>The capacity provider updates failed.</p> </d...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:815:635
[INFO] [stdout]     |
[INFO] [stdout] 815 | ...duler strategy is required if the service is using the <code>CODE<em>DEPLOY</code> or <code>EXTERNAL</code> deployment controller type...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 815 |     /// <p><p>The scheduling strategy to use for the service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Services</a>.</p> <p>There are two service scheduler strategies available:</p> <ul> <li> <p> <code>REPLICA</code>-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service is using the <code>`CODE<em>`DEPLOY</code> or <code>EXTERNAL</code> deployment controller types.</p> </li> <li> <p> <code>DAEMON</code>-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that do not meet the placement constraints. When you&#39;re using this strategy, you don&#39;t need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies.</p> <note> <p>Tasks using the Fargate launch type or the <code>CODE</em>DEPLOY</code> or <code>EXTERNAL</code> deployment controller types don&#39;t support the <code>DAEMON</code> scheduling strategy.</p> </note> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:815:1295
[INFO] [stdout]     |
[INFO] [stdout] 815 | ... <note> <p>Tasks using the Fargate launch type or the <code>CODE</em>DEPLOY</code> or <code>EXTERNAL</code> deployment controller type...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1133:564
[INFO] [stdout]      |
[INFO] [stdout] 1133 | ...ecified in the <a>DeploymentConfiguration</a>.</p> </dd> <dt>CODE<em>DEPLOY</dt> <dd> <p>The blue/green (<code>CODE</em>DEPLOY</code>)...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1133 |     /// <p><p>The deployment controller type to use.</p> <p>There are three deployment controller types available:</p> <dl> <dt>ECS</dt> <dd> <p>The rolling update (<code>ECS</code>) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the <a>DeploymentConfiguration</a>.</p> </dd> <dt>`CODE<em>`DEPLOY</dt> <dd> <p>The blue/green (<code>CODE</em>DEPLOY</code>) deployment type uses the blue/green deployment model powered by AWS CodeDeploy, which allows you to verify a new deployment of a service before sending production traffic to it.</p> </dd> <dt>EXTERNAL</dt> <dd> <p>The external (<code>EXTERNAL</code>) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1133:614
[INFO] [stdout]      |
[INFO] [stdout] 1133 | ...</dd> <dt>CODE<em>DEPLOY</dt> <dd> <p>The blue/green (<code>CODE</em>DEPLOY</code>) deployment type uses the blue/green deployment mod...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: invalid self-closing HTML tag `p`
[INFO] [stdout]     --> src/generated.rs:3752:1578
[INFO] [stdout]      |
[INFO] [stdout] 3752 | ...apacity providers for a cluster after the cluster is created.</p> <p/></p>
[INFO] [stdout]      |                                                                      ^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 9 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 12.03s
[INFO] running `Command { std: "docker" "inspect" "8311154f6911babca4a87d0f14c27a60d8c143ffec4153cda3171ca81a6096fb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "8311154f6911babca4a87d0f14c27a60d8c143ffec4153cda3171ca81a6096fb", kill_on_drop: false }`
[INFO] [stdout] 8311154f6911babca4a87d0f14c27a60d8c143ffec4153cda3171ca81a6096fb
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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" "RUSTC_BOOTSTRAP=1" "-e" "DOCS_RS=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] 9061a1bb04d40aec989a710b36e5c498f05451f75fca6904bc6a62666e332257
[INFO] running `Command { std: "docker" "start" "-a" "9061a1bb04d40aec989a710b36e5c498f05451f75fca6904bc6a62666e332257", kill_on_drop: false }`
[INFO] [stderr]  Documenting rusoto_ecs v0.48.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:177:250
[INFO] [stdout]     |
[INFO] [stdout] 177 | ...provider is in the process of being deleted.</p> </dd> <dt>DELETE<em>COMPLETE</dt> <dd> <p>The capacity provider has been successfully...
[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] 177 |     /// <p><p>The update status of the capacity provider. The following are the possible states that will be returned.</p> <dl> <dt>DELETE<em>IN</em>PROGRESS</dt> <dd> <p>The capacity provider is in the process of being deleted.</p> </dd> <dt>`DELETE<em>`COMPLETE</dt> <dd> <p>The capacity provider has been successfully deleted and will have an <code>INACTIVE</code> status.</p> </dd> <dt>DELETE</em>FAILED</dt> <dd> <p>The capacity provider was unable to be deleted. The update status reason will provide further details about why the delete failed.</p> </dd> </dl></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                    +          +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:177:395
[INFO] [stdout]     |
[INFO] [stdout] 177 | ... will have an <code>INACTIVE</code> status.</p> </dd> <dt>DELETE</em>FAILED</dt> <dd> <p>The capacity provider was unable to be delete...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:215:342
[INFO] [stdout]     |
[INFO] [stdout] 215 | ...ling plan is provisioning or deprovisioning.</p> </dd> <dt>UPDATE<em>COMPLETE</dt> <dd> <p>The capacity providers have successfully up...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 215 |     /// <p><p>The status of the capacity providers associated with the cluster. The following are the states that will be returned:</p> <dl> <dt>UPDATE<em>IN</em>PROGRESS</dt> <dd> <p>The available capacity providers for the cluster are updating. This occurs when the Auto Scaling plan is provisioning or deprovisioning.</p> </dd> <dt>`UPDATE<em>`COMPLETE</dt> <dd> <p>The capacity providers have successfully updated.</p> </dd> <dt>UPDATE</em>FAILED</dt> <dd> <p>The capacity provider updates failed.</p> </dd> </dl></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                +          +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:215:438
[INFO] [stdout]     |
[INFO] [stdout] 215 | ...pacity providers have successfully updated.</p> </dd> <dt>UPDATE</em>FAILED</dt> <dd> <p>The capacity provider updates failed.</p> </d...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:815:635
[INFO] [stdout]     |
[INFO] [stdout] 815 | ...duler strategy is required if the service is using the <code>CODE<em>DEPLOY</code> or <code>EXTERNAL</code> deployment controller type...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 815 |     /// <p><p>The scheduling strategy to use for the service. For more information, see <a href="https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html">Services</a>.</p> <p>There are two service scheduler strategies available:</p> <ul> <li> <p> <code>REPLICA</code>-The replica scheduling strategy places and maintains the desired number of tasks across your cluster. By default, the service scheduler spreads tasks across Availability Zones. You can use task placement strategies and constraints to customize task placement decisions. This scheduler strategy is required if the service is using the <code>`CODE<em>`DEPLOY</code> or <code>EXTERNAL</code> deployment controller types.</p> </li> <li> <p> <code>DAEMON</code>-The daemon scheduling strategy deploys exactly one task on each active container instance that meets all of the task placement constraints that you specify in your cluster. The service scheduler also evaluates the task placement constraints for running tasks and will stop tasks that do not meet the placement constraints. When you&#39;re using this strategy, you don&#39;t need to specify a desired number of tasks, a task placement strategy, or use Service Auto Scaling policies.</p> <note> <p>Tasks using the Fargate launch type or the <code>CODE</em>DEPLOY</code> or <code>EXTERNAL</code> deployment controller types don&#39;t support the <code>DAEMON</code> scheduling strategy.</p> </note> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:815:1295
[INFO] [stdout]     |
[INFO] [stdout] 815 | ... <note> <p>Tasks using the Fargate launch type or the <code>CODE</em>DEPLOY</code> or <code>EXTERNAL</code> deployment controller type...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1133:564
[INFO] [stdout]      |
[INFO] [stdout] 1133 | ...ecified in the <a>DeploymentConfiguration</a>.</p> </dd> <dt>CODE<em>DEPLOY</dt> <dd> <p>The blue/green (<code>CODE</em>DEPLOY</code>)...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1133 |     /// <p><p>The deployment controller type to use.</p> <p>There are three deployment controller types available:</p> <dl> <dt>ECS</dt> <dd> <p>The rolling update (<code>ECS</code>) deployment type involves replacing the current running version of the container with the latest version. The number of containers Amazon ECS adds or removes from the service during a rolling update is controlled by adjusting the minimum and maximum number of healthy tasks allowed during a service deployment, as specified in the <a>DeploymentConfiguration</a>.</p> </dd> <dt>`CODE<em>`DEPLOY</dt> <dd> <p>The blue/green (<code>CODE</em>DEPLOY</code>) deployment type uses the blue/green deployment model powered by AWS CodeDeploy, which allows you to verify a new deployment of a service before sending production traffic to it.</p> </dd> <dt>EXTERNAL</dt> <dd> <p>The external (<code>EXTERNAL</code>) deployment type enables you to use any third-party deployment controller for full control over the deployment process for an Amazon ECS service.</p> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1133:614
[INFO] [stdout]      |
[INFO] [stdout] 1133 | ...</dd> <dt>CODE<em>DEPLOY</dt> <dd> <p>The blue/green (<code>CODE</em>DEPLOY</code>) deployment type uses the blue/green deployment mod...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: invalid self-closing HTML tag `p`
[INFO] [stdout]     --> src/generated.rs:3752:1578
[INFO] [stdout]      |
[INFO] [stdout] 3752 | ...apacity providers for a cluster after the cluster is created.</p> <p/></p>
[INFO] [stdout]      |                                                                      ^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 9 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 3.07s
[INFO] running `Command { std: "docker" "inspect" "9061a1bb04d40aec989a710b36e5c498f05451f75fca6904bc6a62666e332257", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "9061a1bb04d40aec989a710b36e5c498f05451f75fca6904bc6a62666e332257", kill_on_drop: false }`
[INFO] [stdout] 9061a1bb04d40aec989a710b36e5c498f05451f75fca6904bc6a62666e332257
