[INFO] fetching crate mz_rusoto_codebuild 0.46.0...
[INFO] documenting mz_rusoto_codebuild-0.46.0 against 1.69.0 for beta-1.70-rustdoc-1
[INFO] extracting crate mz_rusoto_codebuild 0.46.0 into /workspace/builds/worker-7-tc1/source
[INFO] validating manifest of crates.io crate mz_rusoto_codebuild 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_codebuild 0.46.0
[INFO] finished tweaking crates.io crate mz_rusoto_codebuild 0.46.0
[INFO] tweaked toml for crates.io crate mz_rusoto_codebuild 0.46.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] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded mz_rusoto_mock v0.46.0
[INFO] [stderr]   Downloaded hyper-rustls v0.20.0
[INFO] [stderr]   Downloaded mz_rusoto_credential v0.46.0
[INFO] [stderr]   Downloaded mz_rusoto_signature v0.46.0
[INFO] [stderr]   Downloaded rustls-native-certs v0.3.0
[INFO] [stderr]   Downloaded mz_rusoto_core v0.46.0
[INFO] [stderr]   Downloaded ct-logs v0.6.0
[INFO] [stderr]   Downloaded security-framework v0.4.4
[INFO] [stderr]   Downloaded security-framework-sys v0.4.3
[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] 9efbaffeb157974e294dfd6370fc151173f7b53e57a9cdc14735d41b69f5ff6e
[INFO] running `Command { std: "docker" "start" "-a" "9efbaffeb157974e294dfd6370fc151173f7b53e57a9cdc14735d41b69f5ff6e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "9efbaffeb157974e294dfd6370fc151173f7b53e57a9cdc14735d41b69f5ff6e", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "9efbaffeb157974e294dfd6370fc151173f7b53e57a9cdc14735d41b69f5ff6e", kill_on_drop: false }`
[INFO] [stdout] 9efbaffeb157974e294dfd6370fc151173f7b53e57a9cdc14735d41b69f5ff6e
[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] 18834bea6c0814227b50b22ee789e9932f7f40c9f5cda61735244d40325bb418
[INFO] running `Command { std: "docker" "start" "-a" "18834bea6c0814227b50b22ee789e9932f7f40c9f5cda61735244d40325bb418", kill_on_drop: false }`
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]    Compiling syn v2.0.15
[INFO] [stderr]    Compiling thiserror v1.0.40
[INFO] [stderr]    Compiling standback v0.2.17
[INFO] [stderr]    Compiling proc-macro-hack v0.5.20+deprecated
[INFO] [stderr]    Compiling ucd-trie v0.1.5
[INFO] [stderr]    Compiling const_fn v0.4.9
[INFO] [stderr]     Checking dirs-sys-next v0.1.2
[INFO] [stderr]     Checking time v0.1.45
[INFO] [stderr]    Compiling time v0.2.27
[INFO] [stderr]     Checking crypto-mac v0.10.1
[INFO] [stderr]     Checking dirs-next v2.0.0
[INFO] [stderr]     Checking block-buffer v0.9.0
[INFO] [stderr]     Checking shlex v0.1.1
[INFO] [stderr]     Checking zeroize v1.6.0
[INFO] [stderr]     Checking hmac v0.10.1
[INFO] [stderr]     Checking sha2 v0.9.9
[INFO] [stderr]     Checking md5 v0.7.0
[INFO] [stderr]     Checking xml-rs v0.8.4
[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 openssl v0.10.52
[INFO] [stderr]    Compiling tokio-macros v0.2.6
[INFO] [stderr]     Checking futures-util v0.3.28
[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 pin-project v1.0.12
[INFO] [stderr]     Checking tracing-futures v0.2.5
[INFO] [stderr]    Compiling semver-parser v0.10.2
[INFO] [stderr]     Checking native-tls v0.2.11
[INFO] [stderr]     Checking serde v1.0.160
[INFO] [stderr]    Compiling semver v0.11.0
[INFO] [stderr]    Compiling rustc_version v0.3.3
[INFO] [stderr]     Checking futures-executor v0.3.28
[INFO] [stderr]    Compiling mz_rusoto_core v0.46.0
[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 chrono v0.4.24
[INFO] [stderr]     Checking serde_json v1.0.96
[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_codebuild v0.46.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:178:212
[INFO] [stdout]     |
[INFO] [stdout] 178 | ...code>FAULT</code>: The build faulted.</p> </li> <li> <p> <code>IN<em>PROGRESS</code>: The build is still in progress.</p> </li> <li> <...
[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] 178 |     /// <p><p>The current status of the build. Valid values include:</p> <ul> <li> <p> <code>FAILED</code>: The build failed.</p> </li> <li> <p> <code>FAULT</code>: The build faulted.</p> </li> <li> <p> <code>`IN<em>`PROGRESS</code>: The build is still in progress.</p> </li> <li> <p> <code>STOPPED</code>: The build stopped.</p> </li> <li> <p> <code>SUCCEEDED</code>: The build succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                  +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:178:419
[INFO] [stdout]     |
[INFO] [stdout] 178 | ...EDED</code>: The build succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:344:230
[INFO] [stdout]     |
[INFO] [stdout] 344 | ...AULT</code>: The build phase faulted.</p> </li> <li> <p> <code>IN<em>PROGRESS</code>: The build phase is still in progress.</p> </li> ...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 344 |     /// <p><p>The current status of the build phase. Valid values include:</p> <ul> <li> <p> <code>FAILED</code>: The build phase failed.</p> </li> <li> <p> <code>FAULT</code>: The build phase faulted.</p> </li> <li> <p> <code>`IN<em>`PROGRESS</code>: The build phase is still in progress.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>STOPPED</code>: The build phase stopped.</p> </li> <li> <p> <code>SUCCEEDED</code>: The build phase succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build phase timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                    +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:344:569
[INFO] [stdout]     |
[INFO] [stdout] 344 | ...code>: The build phase succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build phase timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:269
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...: The build has been completed.</p> </li> <li> <p> <code>DOWNLOAD<em>SOURCE</code>: Source code is being downloaded in this build phas...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 348 |     /// <p><p>The name of the build phase. Valid values include:</p> <ul> <li> <p> <code>BUILD</code>: Core build activities typically occur in this build phase.</p> </li> <li> <p> <code>COMPLETED</code>: The build has been completed.</p> </li> <li> <p> <code>`DOWNLOAD<em>`SOURCE</code>: Source code is being downloaded in this build phase.</p> </li> <li> <p> <code>FINALIZING</code>: The build process is completing in this build phase.</p> </li> <li> <p> <code>INSTALL</code>: Installation activities typically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PRE<em>BUILD</code>: Pre-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PROVISIONING</code>: The build environment is being set up.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>SUBMITTED</code>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to the output location.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                     +            +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:569
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...pically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:675
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...typically occur in this build phase.</p> </li> <li> <p> <code>PRE<em>BUILD</code>: Pre-build activities typically occur in this build ...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 348 |     /// <p><p>The name of the build phase. Valid values include:</p> <ul> <li> <p> <code>BUILD</code>: Core build activities typically occur in this build phase.</p> </li> <li> <p> <code>COMPLETED</code>: The build has been completed.</p> </li> <li> <p> <code>DOWNLOAD<em>SOURCE</code>: Source code is being downloaded in this build phase.</p> </li> <li> <p> <code>FINALIZING</code>: The build process is completing in this build phase.</p> </li> <li> <p> <code>INSTALL</code>: Installation activities typically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build phase.</p> </li> <li> <p> <code>`PRE<em>`BUILD</code>: Pre-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PROVISIONING</code>: The build environment is being set up.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>SUBMITTED</code>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to the output location.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +       +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:1054
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to th...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:686:104
[INFO] [stdout]     |
[INFO] [stdout] 686 |     /// <p><p>The type of environment variable. Valid values include:</p> <ul> <li> <p> <code>PARAMETER<em>STORE</code>: An environment v...
[INFO] [stdout]     |                                                                                                        ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 686 |     /// <p><p>The type of environment variable. Valid values include:</p> <ul> <li> <p> <code>`PARAMETER<em>`STORE</code>: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see <a href="https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#parameter-store-build-spec"> parameter store reference-key in the buildspec file</a>.</p> </li> <li> <p> <code>PLAINTEXT</code>: An environment variable in plain text format. This is the default value.</p> </li> <li> <p> <code>SECRETS</em>MANAGER</code>: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see <a href="https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#secrets-manager-build-spec"> secrets manager reference-key in the buildspec file</a>.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                               +             +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:686:586
[INFO] [stdout]     |
[INFO] [stdout] 686 | ...mat. This is the default value.</p> </li> <li> <p> <code>SECRETS</em>MANAGER</code>: An environment variable stored in AWS Secrets Man...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:690:477
[INFO] [stdout]     |
[INFO] [stdout] 690 | ...recommend you use an environment variable of type <code>PARAMETER<em>STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </importan...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 690 |     /// <p><p>The value of the environment variable.</p> <important> <p>We strongly discourage the use of <code>PLAINTEXT</code> environment variables to store sensitive values, especially AWS secret key IDs and secret access keys. <code>PLAINTEXT</code> environment variables can be displayed in plain text using the AWS CodeBuild console and the AWS Command Line Interface (AWS CLI). For sensitive values, we recommend you use an environment variable of type <code>`PARAMETER<em>`STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </important></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    +             +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:690:510
[INFO] [stdout]     |
[INFO] [stdout] 690 | ...ariable of type <code>PARAMETER<em>STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </important></p>
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:703:288
[INFO] [stdout]     |
[INFO] [stdout] 703 | ...t of the <code>install</code> phase and the end of the <code>post<em>build</code> phase. After the <code>post</em>build</code> phase e...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 703 |     /// <p><p> The value assigned to this exported environment variable. </p> <note> <p> During a build, the value of a variable is available starting with the <code>install</code> phase. It can be updated between the start of the <code>install</code> phase and the end of the <code>`post<em>`build</code> phase. After the <code>post</em>build</code> phase ends, the value of exported variables cannot change.</p> </note></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                            +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:703:332
[INFO] [stdout]     |
[INFO] [stdout] 703 | ...nd of the <code>post<em>build</code> phase. After the <code>post</em>build</code> phase ends, the value of exported variables cannot c...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:886:124
[INFO] [stdout]     |
[INFO] [stdout] 886 |     /// <p><p> The criterion to be used to list build report groups. Valid values include: </p> <ul> <li> <p> <code>CREATED<em>TIME</code...
[INFO] [stdout]     |                                                                                                                            ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 886 |     /// <p><p> The criterion to be used to list build report groups. Valid values include: </p> <ul> <li> <p> <code>`CREATED<em>`TIME</code>: List based on when each report group was created.</p> </li> <li> <p> <code>LAST</em>MODIFIED_TIME</code>: List based on when each report group was last changed.</p> </li> <li> <p> <code>NAME</code>: List based on each report group&#39;s name.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                     +           +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:886:220
[INFO] [stdout]     |
[INFO] [stdout] 886 | ...hen each report group was created.</p> </li> <li> <p> <code>LAST</em>MODIFIED_TIME</code>: List based on when each report group was la...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1253:423
[INFO] [stdout]      |
[INFO] [stdout] 1253 | ...eBuild.</p> </li> <li> <p>If <code>type</code> is set to <code>NO<em>ARTIFACTS</code>, this value is ignored if specified, because no ...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1253 |     /// <p><p>Along with <code>path</code> and <code>namespaceType</code>, the pattern that AWS CodeBuild uses to name and store the output artifact:</p> <ul> <li> <p>If <code>type</code> is set to <code>CODEPIPELINE</code>, AWS CodePipeline ignores this value if specified. This is because AWS CodePipeline manages its build output names instead of AWS CodeBuild.</p> </li> <li> <p>If <code>type</code> is set to <code>`NO<em>`ARTIFACTS</code>, this value is ignored if specified, because no build output is produced.</p> </li> <li> <p>If <code>type</code> is set to <code>S3</code>, this is the name of the output artifact object. If you set the name to be a forward slash (&quot;/&quot;), the artifact is stored in the root of the output bucket.</p> </li> </ul> <p>For example:</p> <ul> <li> <p> If <code>path</code> is set to <code>MyArtifacts</code>, <code>namespaceType</code> is set to <code>BUILD</em>ID</code>, and <code>name</code> is set to <code>MyArtifact.zip</code>, then the output artifact is stored in <code>MyArtifacts/<i>build-ID</i>/MyArtifact.zip</code>. </p> </li> <li> <p> If <code>path</code> is empty, <code>namespaceType</code> is set to <code>NONE</code>, and <code>name</code> is set to &quot;<code>/</code>&quot;, the output artifact is stored in the root of the output bucket. </p> </li> <li> <p> If <code>path</code> is set to <code>MyArtifacts</code>, <code>namespaceType</code> is set to <code>BUILD_ID</code>, and <code>name</code> is set to &quot;<code>/</code>&quot;, the output artifact is stored in <code>MyArtifacts/<i>build-ID</i> </code>. </p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                     +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1253:903
[INFO] [stdout]      |
[INFO] [stdout] 1253 | ...tifacts</code>, <code>namespaceType</code> is set to <code>BUILD</em>ID</code>, and <code>name</code> is set to <code>MyArtifact.zip</...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1299:645
[INFO] [stdout]      |
[INFO] [stdout] 1299 | ...n is ignored. </p> </li> <li> <p> <code>LOCAL<em>DOCKER</em>LAYER<em>CACHE</code> mode caches existing Docker layers. This mode is a g...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1299 |     /// <p><p> If you use a <code>LOCAL</code> cache, the local cache mode. You can use one or more local cache modes at the same time. </p> <ul> <li> <p> <code>LOCAL<em>SOURCE</em>CACHE</code> mode caches Git metadata for primary and secondary sources. After the cache is created, subsequent builds pull only the change between commits. This mode is a good choice for projects with a clean working directory and a source that is a large Git repository. If you choose this option and your project does not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket), the option is ignored. </p> </li> <li> <p> <code>LOCAL<em>DOCKER</em>`LAYER<em>`CACHE</code> mode caches existing Docker layers. This mode is a good choice for projects that build or pull large Docker images. It can prevent the performance issues caused by pulling large Docker images down from the network. </p> <note> <ul> <li> <p> You can use a Docker layer cache in the Linux environment only. </p> </li> <li> <p> The <code>privileged</code> flag must be set so that your project has the required Docker permissions. </p> </li> <li> <p> You should consider the security implications before you use a Docker layer cache. </p> </li> </ul> </note> </li> </ul> <ul> <li> <p> <code>LOCAL</em>CUSTOM_CACHE</code> mode caches directories you specify in the buildspec file. This mode is a good choice if your build scenario is not suited to one of the other three local cache modes. If you use a custom cache: </p> <ul> <li> <p> Only directories can be specified for caching. You cannot specify individual files. </p> </li> <li> <p> Symlinks are used to reference cached directories. </p> </li> <li> <p> Cached directories are linked to your build before it downloads its project sources. Cached items are overridden if a source item has the same name. Directories are specified using cache paths in the buildspec file. </p> </li> </ul> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +         +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1299:1255
[INFO] [stdout]      |
[INFO] [stdout] 1299 | .... </p> </li> </ul> </note> </li> </ul> <ul> <li> <p> <code>LOCAL</em>CUSTOM_CACHE</code> mode caches directories you specify in the bu...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1337:119
[INFO] [stdout]      |
[INFO] [stdout] 1337 |     /// <p><p>The type of build environment to use for related builds.</p> <ul> <li> <p>The environment type <code>ARM<em>CONTAINER</code...
[INFO] [stdout]      |                                                                                                                       ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1337 |     /// <p><p>The type of build environment to use for related builds.</p> <ul> <li> <p>The environment type <code>`ARM<em>`CONTAINER</code> is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Sydney), and EU (Frankfurt).</p> </li> <li> <p>The environment type <code>LINUX</em>CONTAINER</code> with compute type <code>build.general1.2xlarge</code> is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), EU (Ireland), EU (London), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), China (Beijing), and China (Ningxia).</p> </li> <li> <p>The environment type <code>LINUX<em>GPU</em>CONTAINER</code> is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), EU (Ireland), EU (London), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney) , China (Beijing), and China (Ningxia).</p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                    +       +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1337:378
[INFO] [stdout]      |
[INFO] [stdout] 1337 | ... (Frankfurt).</p> </li> <li> <p>The environment type <code>LINUX</em>CONTAINER</code> with compute type <code>build.general1.2xlarge</...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1406:569
[INFO] [stdout]      |
[INFO] [stdout] 1406 | ...tHub Enterprise Cloud repository.</p> </li> <li> <p> <code>GITHUB<em>ENTERPRISE</code>: The source code is in a GitHub Enterprise Serv...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1406 |     /// <p><p>The type of repository that contains the source code to be built. Valid values include:</p> <ul> <li> <p> <code>BITBUCKET</code>: The source code is in a Bitbucket repository.</p> </li> <li> <p> <code>CODECOMMIT</code>: The source code is in an AWS CodeCommit repository.</p> </li> <li> <p> <code>CODEPIPELINE</code>: The source code settings are specified in the source action of a pipeline in AWS CodePipeline.</p> </li> <li> <p> <code>GITHUB</code>: The source code is in a GitHub or GitHub Enterprise Cloud repository.</p> </li> <li> <p> <code>`GITHUB<em>`ENTERPRISE</code>: The source code is in a GitHub Enterprise Server repository.</p> </li> <li> <p> <code>NO</em>SOURCE</code>: The project does not have input source code.</p> </li> <li> <p> <code>S3</code>: The source code is in an Amazon Simple Storage Service (Amazon S3) input bucket.</p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   +          +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1406:680
[INFO] [stdout]      |
[INFO] [stdout] 1406 | ...GitHub Enterprise Server repository.</p> </li> <li> <p> <code>NO</em>SOURCE</code>: The project does not have input source code.</p> <...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:148
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...de>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>,...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>`HEAD<em>`REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:174
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...R<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSA...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:201
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ..., <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> ...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>`FILE<em>`PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                     +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:234
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook eve...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:1159
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> `HEAD<em>`REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:1547
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...et push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:1812
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> `FILE<em>`PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:2172
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...ub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head com...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 32 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 27.38s
[INFO] running `Command { std: "docker" "inspect" "18834bea6c0814227b50b22ee789e9932f7f40c9f5cda61735244d40325bb418", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "18834bea6c0814227b50b22ee789e9932f7f40c9f5cda61735244d40325bb418", kill_on_drop: false }`
[INFO] [stdout] 18834bea6c0814227b50b22ee789e9932f7f40c9f5cda61735244d40325bb418
[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] 8a782563b28f4dd555e9f58d03e2c9388cb9eff6467dd5e0be1d7107b6c96a26
[INFO] running `Command { std: "docker" "start" "-a" "8a782563b28f4dd555e9f58d03e2c9388cb9eff6467dd5e0be1d7107b6c96a26", kill_on_drop: false }`
[INFO] [stderr]  Documenting mz_rusoto_codebuild v0.46.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:178:212
[INFO] [stdout]     |
[INFO] [stdout] 178 | ...code>FAULT</code>: The build faulted.</p> </li> <li> <p> <code>IN<em>PROGRESS</code>: The build is still in progress.</p> </li> <li> <...
[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] 178 |     /// <p><p>The current status of the build. Valid values include:</p> <ul> <li> <p> <code>FAILED</code>: The build failed.</p> </li> <li> <p> <code>FAULT</code>: The build faulted.</p> </li> <li> <p> <code>`IN<em>`PROGRESS</code>: The build is still in progress.</p> </li> <li> <p> <code>STOPPED</code>: The build stopped.</p> </li> <li> <p> <code>SUCCEEDED</code>: The build succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                  +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:178:419
[INFO] [stdout]     |
[INFO] [stdout] 178 | ...EDED</code>: The build succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:344:230
[INFO] [stdout]     |
[INFO] [stdout] 344 | ...AULT</code>: The build phase faulted.</p> </li> <li> <p> <code>IN<em>PROGRESS</code>: The build phase is still in progress.</p> </li> ...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 344 |     /// <p><p>The current status of the build phase. Valid values include:</p> <ul> <li> <p> <code>FAILED</code>: The build phase failed.</p> </li> <li> <p> <code>FAULT</code>: The build phase faulted.</p> </li> <li> <p> <code>`IN<em>`PROGRESS</code>: The build phase is still in progress.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>STOPPED</code>: The build phase stopped.</p> </li> <li> <p> <code>SUCCEEDED</code>: The build phase succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build phase timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                    +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:344:569
[INFO] [stdout]     |
[INFO] [stdout] 344 | ...code>: The build phase succeeded.</p> </li> <li> <p> <code>TIMED</em>OUT</code>: The build phase timed out.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:269
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...: The build has been completed.</p> </li> <li> <p> <code>DOWNLOAD<em>SOURCE</code>: Source code is being downloaded in this build phas...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 348 |     /// <p><p>The name of the build phase. Valid values include:</p> <ul> <li> <p> <code>BUILD</code>: Core build activities typically occur in this build phase.</p> </li> <li> <p> <code>COMPLETED</code>: The build has been completed.</p> </li> <li> <p> <code>`DOWNLOAD<em>`SOURCE</code>: Source code is being downloaded in this build phase.</p> </li> <li> <p> <code>FINALIZING</code>: The build process is completing in this build phase.</p> </li> <li> <p> <code>INSTALL</code>: Installation activities typically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PRE<em>BUILD</code>: Pre-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PROVISIONING</code>: The build environment is being set up.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>SUBMITTED</code>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to the output location.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                     +            +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:569
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...pically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:675
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...typically occur in this build phase.</p> </li> <li> <p> <code>PRE<em>BUILD</code>: Pre-build activities typically occur in this build ...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 348 |     /// <p><p>The name of the build phase. Valid values include:</p> <ul> <li> <p> <code>BUILD</code>: Core build activities typically occur in this build phase.</p> </li> <li> <p> <code>COMPLETED</code>: The build has been completed.</p> </li> <li> <p> <code>DOWNLOAD<em>SOURCE</code>: Source code is being downloaded in this build phase.</p> </li> <li> <p> <code>FINALIZING</code>: The build process is completing in this build phase.</p> </li> <li> <p> <code>INSTALL</code>: Installation activities typically occur in this build phase.</p> </li> <li> <p> <code>POST</em>BUILD</code>: Post-build activities typically occur in this build phase.</p> </li> <li> <p> <code>`PRE<em>`BUILD</code>: Pre-build activities typically occur in this build phase.</p> </li> <li> <p> <code>PROVISIONING</code>: The build environment is being set up.</p> </li> <li> <p> <code>QUEUED</code>: The build has been submitted and is queued behind other submitted builds.</p> </li> <li> <p> <code>SUBMITTED</code>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to the output location.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +       +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:348:1054
[INFO] [stdout]     |
[INFO] [stdout] 348 | ...>: The build has been submitted.</p> </li> <li> <p> <code>UPLOAD</em>ARTIFACTS</code>: Build output artifacts are being uploaded to th...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:686:104
[INFO] [stdout]     |
[INFO] [stdout] 686 |     /// <p><p>The type of environment variable. Valid values include:</p> <ul> <li> <p> <code>PARAMETER<em>STORE</code>: An environment v...
[INFO] [stdout]     |                                                                                                        ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 686 |     /// <p><p>The type of environment variable. Valid values include:</p> <ul> <li> <p> <code>`PARAMETER<em>`STORE</code>: An environment variable stored in Amazon EC2 Systems Manager Parameter Store. To learn how to specify a parameter store environment variable, see <a href="https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#parameter-store-build-spec"> parameter store reference-key in the buildspec file</a>.</p> </li> <li> <p> <code>PLAINTEXT</code>: An environment variable in plain text format. This is the default value.</p> </li> <li> <p> <code>SECRETS</em>MANAGER</code>: An environment variable stored in AWS Secrets Manager. To learn how to specify a secrets manager environment variable, see <a href="https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html#secrets-manager-build-spec"> secrets manager reference-key in the buildspec file</a>.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                               +             +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:686:586
[INFO] [stdout]     |
[INFO] [stdout] 686 | ...mat. This is the default value.</p> </li> <li> <p> <code>SECRETS</em>MANAGER</code>: An environment variable stored in AWS Secrets Man...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:690:477
[INFO] [stdout]     |
[INFO] [stdout] 690 | ...recommend you use an environment variable of type <code>PARAMETER<em>STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </importan...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 690 |     /// <p><p>The value of the environment variable.</p> <important> <p>We strongly discourage the use of <code>PLAINTEXT</code> environment variables to store sensitive values, especially AWS secret key IDs and secret access keys. <code>PLAINTEXT</code> environment variables can be displayed in plain text using the AWS CodeBuild console and the AWS Command Line Interface (AWS CLI). For sensitive values, we recommend you use an environment variable of type <code>`PARAMETER<em>`STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </important></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    +             +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:690:510
[INFO] [stdout]     |
[INFO] [stdout] 690 | ...ariable of type <code>PARAMETER<em>STORE</code> or <code>SECRETS</em>MANAGER</code>. </p> </important></p>
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:703:288
[INFO] [stdout]     |
[INFO] [stdout] 703 | ...t of the <code>install</code> phase and the end of the <code>post<em>build</code> phase. After the <code>post</em>build</code> phase e...
[INFO] [stdout]     |                                                                     ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 703 |     /// <p><p> The value assigned to this exported environment variable. </p> <note> <p> During a build, the value of a variable is available starting with the <code>install</code> phase. It can be updated between the start of the <code>install</code> phase and the end of the <code>`post<em>`build</code> phase. After the <code>post</em>build</code> phase ends, the value of exported variables cannot change.</p> </note></p>
[INFO] [stdout]     |                                                                                                                                                                                                                                                                                            +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:703:332
[INFO] [stdout]     |
[INFO] [stdout] 703 | ...nd of the <code>post<em>build</code> phase. After the <code>post</em>build</code> phase ends, the value of exported variables cannot c...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:886:124
[INFO] [stdout]     |
[INFO] [stdout] 886 |     /// <p><p> The criterion to be used to list build report groups. Valid values include: </p> <ul> <li> <p> <code>CREATED<em>TIME</code...
[INFO] [stdout]     |                                                                                                                            ^^^^
[INFO] [stdout]     |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]     |
[INFO] [stdout] 886 |     /// <p><p> The criterion to be used to list build report groups. Valid values include: </p> <ul> <li> <p> <code>`CREATED<em>`TIME</code>: List based on when each report group was created.</p> </li> <li> <p> <code>LAST</em>MODIFIED_TIME</code>: List based on when each report group was last changed.</p> </li> <li> <p> <code>NAME</code>: List based on each report group&#39;s name.</p> </li> </ul></p>
[INFO] [stdout]     |                                                                                                                     +           +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]    --> src/generated.rs:886:220
[INFO] [stdout]     |
[INFO] [stdout] 886 | ...hen each report group was created.</p> </li> <li> <p> <code>LAST</em>MODIFIED_TIME</code>: List based on when each report group was la...
[INFO] [stdout]     |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1253:423
[INFO] [stdout]      |
[INFO] [stdout] 1253 | ...eBuild.</p> </li> <li> <p>If <code>type</code> is set to <code>NO<em>ARTIFACTS</code>, this value is ignored if specified, because no ...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1253 |     /// <p><p>Along with <code>path</code> and <code>namespaceType</code>, the pattern that AWS CodeBuild uses to name and store the output artifact:</p> <ul> <li> <p>If <code>type</code> is set to <code>CODEPIPELINE</code>, AWS CodePipeline ignores this value if specified. This is because AWS CodePipeline manages its build output names instead of AWS CodeBuild.</p> </li> <li> <p>If <code>type</code> is set to <code>`NO<em>`ARTIFACTS</code>, this value is ignored if specified, because no build output is produced.</p> </li> <li> <p>If <code>type</code> is set to <code>S3</code>, this is the name of the output artifact object. If you set the name to be a forward slash (&quot;/&quot;), the artifact is stored in the root of the output bucket.</p> </li> </ul> <p>For example:</p> <ul> <li> <p> If <code>path</code> is set to <code>MyArtifacts</code>, <code>namespaceType</code> is set to <code>BUILD</em>ID</code>, and <code>name</code> is set to <code>MyArtifact.zip</code>, then the output artifact is stored in <code>MyArtifacts/<i>build-ID</i>/MyArtifact.zip</code>. </p> </li> <li> <p> If <code>path</code> is empty, <code>namespaceType</code> is set to <code>NONE</code>, and <code>name</code> is set to &quot;<code>/</code>&quot;, the output artifact is stored in the root of the output bucket. </p> </li> <li> <p> If <code>path</code> is set to <code>MyArtifacts</code>, <code>namespaceType</code> is set to <code>BUILD_ID</code>, and <code>name</code> is set to &quot;<code>/</code>&quot;, the output artifact is stored in <code>MyArtifacts/<i>build-ID</i> </code>. </p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                     +      +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1253:903
[INFO] [stdout]      |
[INFO] [stdout] 1253 | ...tifacts</code>, <code>namespaceType</code> is set to <code>BUILD</em>ID</code>, and <code>name</code> is set to <code>MyArtifact.zip</...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1299:645
[INFO] [stdout]      |
[INFO] [stdout] 1299 | ...n is ignored. </p> </li> <li> <p> <code>LOCAL<em>DOCKER</em>LAYER<em>CACHE</code> mode caches existing Docker layers. This mode is a g...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1299 |     /// <p><p> If you use a <code>LOCAL</code> cache, the local cache mode. You can use one or more local cache modes at the same time. </p> <ul> <li> <p> <code>LOCAL<em>SOURCE</em>CACHE</code> mode caches Git metadata for primary and secondary sources. After the cache is created, subsequent builds pull only the change between commits. This mode is a good choice for projects with a clean working directory and a source that is a large Git repository. If you choose this option and your project does not use a Git repository (GitHub, GitHub Enterprise, or Bitbucket), the option is ignored. </p> </li> <li> <p> <code>LOCAL<em>DOCKER</em>`LAYER<em>`CACHE</code> mode caches existing Docker layers. This mode is a good choice for projects that build or pull large Docker images. It can prevent the performance issues caused by pulling large Docker images down from the network. </p> <note> <ul> <li> <p> You can use a Docker layer cache in the Linux environment only. </p> </li> <li> <p> The <code>privileged</code> flag must be set so that your project has the required Docker permissions. </p> </li> <li> <p> You should consider the security implications before you use a Docker layer cache. </p> </li> </ul> </note> </li> </ul> <ul> <li> <p> <code>LOCAL</em>CUSTOM_CACHE</code> mode caches directories you specify in the buildspec file. This mode is a good choice if your build scenario is not suited to one of the other three local cache modes. If you use a custom cache: </p> <ul> <li> <p> Only directories can be specified for caching. You cannot specify individual files. </p> </li> <li> <p> Symlinks are used to reference cached directories. </p> </li> <li> <p> Cached directories are linked to your build before it downloads its project sources. Cached items are overridden if a source item has the same name. Directories are specified using cache paths in the buildspec file. </p> </li> </ul> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +         +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1299:1255
[INFO] [stdout]      |
[INFO] [stdout] 1299 | .... </p> </li> </ul> </note> </li> </ul> <ul> <li> <p> <code>LOCAL</em>CUSTOM_CACHE</code> mode caches directories you specify in the bu...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1337:119
[INFO] [stdout]      |
[INFO] [stdout] 1337 |     /// <p><p>The type of build environment to use for related builds.</p> <ul> <li> <p>The environment type <code>ARM<em>CONTAINER</code...
[INFO] [stdout]      |                                                                                                                       ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1337 |     /// <p><p>The type of build environment to use for related builds.</p> <ul> <li> <p>The environment type <code>`ARM<em>`CONTAINER</code> is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Sydney), and EU (Frankfurt).</p> </li> <li> <p>The environment type <code>LINUX</em>CONTAINER</code> with compute type <code>build.general1.2xlarge</code> is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), EU (Ireland), EU (London), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), China (Beijing), and China (Ningxia).</p> </li> <li> <p>The environment type <code>LINUX<em>GPU</em>CONTAINER</code> is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Canada (Central), EU (Ireland), EU (London), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney) , China (Beijing), and China (Ningxia).</p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                    +       +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1337:378
[INFO] [stdout]      |
[INFO] [stdout] 1337 | ... (Frankfurt).</p> </li> <li> <p>The environment type <code>LINUX</em>CONTAINER</code> with compute type <code>build.general1.2xlarge</...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1406:569
[INFO] [stdout]      |
[INFO] [stdout] 1406 | ...tHub Enterprise Cloud repository.</p> </li> <li> <p> <code>GITHUB<em>ENTERPRISE</code>: The source code is in a GitHub Enterprise Serv...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 1406 |     /// <p><p>The type of repository that contains the source code to be built. Valid values include:</p> <ul> <li> <p> <code>BITBUCKET</code>: The source code is in a Bitbucket repository.</p> </li> <li> <p> <code>CODECOMMIT</code>: The source code is in an AWS CodeCommit repository.</p> </li> <li> <p> <code>CODEPIPELINE</code>: The source code settings are specified in the source action of a pipeline in AWS CodePipeline.</p> </li> <li> <p> <code>GITHUB</code>: The source code is in a GitHub or GitHub Enterprise Cloud repository.</p> </li> <li> <p> <code>`GITHUB<em>`ENTERPRISE</code>: The source code is in a GitHub Enterprise Server repository.</p> </li> <li> <p> <code>NO</em>SOURCE</code>: The project does not have input source code.</p> </li> <li> <p> <code>S3</code>: The source code is in an Amazon Simple Storage Service (Amazon S3) input bucket.</p> </li> </ul></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   +          +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:1406:680
[INFO] [stdout]      |
[INFO] [stdout] 1406 | ...GitHub Enterprise Server repository.</p> </li> <li> <p> <code>NO</em>SOURCE</code>: The project does not have input source code.</p> <...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:148
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...de>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>,...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>`HEAD<em>`REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:174
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...R<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSA...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:201
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ..., <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> ...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>`FILE<em>`PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                     +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:234
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook eve...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:1159
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> `HEAD<em>`REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:1547
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...et push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unclosed HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:1812
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...Works with pull request events only. </p> </note> </dd> <dt> FILE<em>PATH </dt> <dd> <p> A webhook triggers a build when the path of a...
[INFO] [stdout]      |                                                                     ^^^^
[INFO] [stdout]      |
[INFO] [stdout] help: try marking as source code
[INFO] [stdout]      |
[INFO] [stdout] 2057 |     /// <p><p> The type of webhook filter. There are six webhook filter types: <code>EVENT</code>, <code>ACTOR<em>ACCOUNT</em>ID</code>, <code>HEAD<em>REF</code>, <code>BASE</em>REF</code>, <code>FILE<em>PATH</code>, and <code>COMMIT</em>MESSAGE</code>. </p> <dl> <dt> EVENT </dt> <dd> <p> A webhook event triggers a build when the provided <code>pattern</code> matches one of five event types: <code>PUSH</code>, <code>PULL<em>REQUEST</em>CREATED</code>, <code>PULL<em>REQUEST</em>UPDATED</code>, <code>PULL<em>REQUEST</em>REOPENED</code>, and <code>PULL<em>REQUEST</em>MERGED</code>. The <code>EVENT</code> patterns are specified as a comma-separated string. For example, <code>PUSH, PULL<em>REQUEST</em>CREATED, PULL<em>REQUEST</em>UPDATED</code> filters all push, pull request created, and pull request updated events. </p> <note> <p> The <code>PULL<em>REQUEST</em>REOPENED</code> works with GitHub and GitHub Enterprise only. </p> </note> </dd> <dt> ACTOR<em>ACCOUNT</em>ID </dt> <dd> <p> A webhook event triggers a build when a GitHub, GitHub Enterprise, or Bitbucket account ID matches the regular expression <code>pattern</code>. </p> </dd> <dt> HEAD<em>REF </dt> <dd> <p> A webhook event triggers a build when the head reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code> and <code>refs/tags/tag-name</code>. </p> <p> Works with GitHub and GitHub Enterprise push, GitHub and GitHub Enterprise pull request, Bitbucket push, and Bitbucket pull request events. </p> </dd> <dt> BASE</em>REF </dt> <dd> <p> A webhook event triggers a build when the base reference matches the regular expression <code>pattern</code>. For example, <code>refs/heads/branch-name</code>. </p> <note> <p> Works with pull request events only. </p> </note> </dd> <dt> `FILE<em>`PATH </dt> <dd> <p> A webhook triggers a build when the path of a changed file matches the regular expression <code>pattern</code>. </p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head commit message matches the regular expression <code>pattern</code>.</p> <note> <p> Works with GitHub and Bitbucket events push and pull requests events. Also works with GitHub Enterprise push events, but does not work with GitHub Enterprise pull request events. </p> </note> </dd> </dl></p>
[INFO] [stdout]      |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                +        +
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unopened HTML tag `em`
[INFO] [stdout]     --> src/generated.rs:2057:2172
[INFO] [stdout]      |
[INFO] [stdout] 2057 | ...ub Enterprise pull request events. </p> </note> </dd> <dt>COMMIT</em>MESSAGE</dt> <dd> <p>A webhook triggers a build when the head com...
[INFO] [stdout]      |                                                                    ^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: 32 warnings emitted
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished dev [unoptimized + debuginfo] target(s) in 2.43s
[INFO] running `Command { std: "docker" "inspect" "8a782563b28f4dd555e9f58d03e2c9388cb9eff6467dd5e0be1d7107b6c96a26", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "8a782563b28f4dd555e9f58d03e2c9388cb9eff6467dd5e0be1d7107b6c96a26", kill_on_drop: false }`
[INFO] [stdout] 8a782563b28f4dd555e9f58d03e2c9388cb9eff6467dd5e0be1d7107b6c96a26
