Executive Status
EnvEnvironment partition: dev, int, stg, or prod. | GoalConfigured success target and run scope for this environment. INT/STG/PROD use all E2E job runs. DEV uses post-good runs plus Tide batches: runs on the final commit of a PR that later merged, or batch retests of PRs that passed their individual e2e-parallel checks. | RunsNumber of job runs in the selected goal definition for this environment. | SuccessSuccess rate on the selected goal definition: (runs - failed runs) / runs * 100. | Gap vs targetDifference in percentage points between current success and the configured target rate. | Change vs prevHow much the success rate changed compared with the immediately preceding equal-length window, using the same goal definition as this row. | Provision successProvisioning here means infrastructure setup before E2E tests start. A run counts as provision-successful if it got past provisioning, even if it later failed during E2E. Runs that failed for 'Other' CI-infrastructure reasons are excluded because those runs never reached the provision step. DEV rows use post-good runs plus Tide batches. INT/STG/PROD show n/a because provisioning is not part of those environments. | Provision change vs prevChange in provision success, in percentage points, compared with the previous equal-length window. Uses the same provision-success definition as the Provision success column. DEV only; INT/STG/PROD show n/a. | E2E successAmong runs that reached E2E execution, this shows how many completed successfully. Provision failures and 'Other' CI-infrastructure failures are excluded because those runs never reached the E2E step. DEV rows use only runs after the final push to a PR that later merged. INT/STG/PROD use all E2E job runs. | E2E success vs prevChange in E2E success, in percentage points, compared with the previous equal-length window. Uses the same E2E-success definition as the E2E success column. |
|---|---|---|---|---|---|---|---|---|---|
| DEV | 95% - Post-good runs + Tide batches | 194 | 22.16% (off track) | -72.84pp | n/a | 100.00% (43/43) | n/a | 100.00% (43/43) | n/a |
| INT | 95% - All E2E job runs | 17 | 76.47% (off track) | -18.53pp | n/a | n/a | n/a | 100.00% (13/13) | n/a |
| STG | 95% - All E2E job runs | 16 | 12.50% (off track) | -82.50pp | n/a | n/a | n/a | 100.00% (2/2) | n/a |
| PROD | 95% - All E2E job runs | 13 | 0.00% (off track) | -95.00pp | n/a | n/a | n/a | n/a | n/a |
Environment: DEV
E2E Jobs
451
Success Rate
16.19%
Provision success
Provisioning here means infrastructure setup before E2E tests start. A run counts as provision-successful if it got past provisioning, even if it later failed during E2E. Runs that failed for 'Other' CI-infrastructure reasons are excluded because those runs never reached the provision step.100.00% (73/73)
E2E success
Among runs that reached E2E execution, this shows how many completed successfully. Provision failures and 'Other' CI-infrastructure failures are excluded because those runs never reached the E2E step.100.00% (73/73)
E2E Jobs (post-good + batches)
These PR-regression-filtered DEV metrics include runs on the final commit of a PR that later merged, plus Tide batch retests of PRs that passed their individual e2e-parallel checks. Each run counts once. This card shows the number of runs in that DEV-only goal basis.194
Success Rate (post-good + batches)
These PR-regression-filtered DEV metrics include runs on the final commit of a PR that later merged, plus Tide batch retests of PRs that passed their individual e2e-parallel checks. Each run counts once. This card shows the overall success rate for that DEV-only goal basis.22.16%
Provision success (post-good + batches)
These PR-regression-filtered DEV metrics include runs on the final commit of a PR that later merged, plus Tide batch retests of PRs that passed their individual e2e-parallel checks. Each run counts once. Provisioning here means infrastructure setup before E2E tests start. A run counts as provision-successful if it got past provisioning, even if it later failed during E2E. Runs that failed for 'Other' CI-infrastructure reasons are excluded because those runs never reached the provision step.100.00% (43/43)
E2E success (post-good + batches)
These PR-regression-filtered DEV metrics include runs on the final commit of a PR that later merged, plus Tide batch retests of PRs that passed their individual e2e-parallel checks. Each run counts once. Among runs that reached E2E execution, this shows how many completed successfully. Provision failures and 'Other' CI-infrastructure failures are excluded because those runs never reached the E2E step.100.00% (43/43)
Daily Run Outcomes
Successful runs
Provision failures
E2E failures
Other failures
Daily Run Outcomes for DEV Goal Basis (post-good + batches)
Successful runs (post-good + batches)
Provision failures
E2E failures
Other failures
No tests below 95.00% in this window with at least 10 runs.
Up to 50 failure patterns are loaded (minimum 1.00% impact), with 10 shown by default. Click column headers to re-sort.
Jump to the full Failure Patterns view for this window
No failure patterns available for this environment in the selected window.
Environment: INT
E2E Jobs
17
Success Rate
76.47%
E2E success
Among runs that reached E2E execution, this shows how many completed successfully. Provision failures and 'Other' CI-infrastructure failures are excluded because those runs never reached the E2E step.100.00% (13/13)
Daily Run Outcomes
Successful runs
Provision failures
E2E failures
Other failures
No tests below 95.00% in this window with at least 10 runs.
Up to 50 failure patterns are loaded (minimum 1.00% impact), with 10 shown by default. Click column headers to re-sort.
Jump to the full Failure Patterns view for this window
No failure patterns available for this environment in the selected window.
Environment: STG
E2E Jobs
16
Success Rate
12.50%
E2E success
Among runs that reached E2E execution, this shows how many completed successfully. Provision failures and 'Other' CI-infrastructure failures are excluded because those runs never reached the E2E step.100.00% (2/2)
Daily Run Outcomes
Successful runs
Provision failures
E2E failures
Other failures
| Pass rate | Runs | Date (UTC) | Suite | Test |
|---|---|---|---|---|
| 50.00% | 14 | stage/parallel | Customer should be able to create an HCP cluster with custom autoscaling and update the autoscaling configuration | |
| 50.00% | 14 | stage/parallel | Customer should create a cluster with private KAS and verify API server is only reachable from VNet while ingress remains public | |
| 57.14% | 14 | stage/parallel | Authorized CIDRs Connectivity should allow API access only from authorized VM IP | |
| 57.14% | 14 | stage/parallel | Customer should be able to create a cluster and node pools with aggregated advanced features | |
| 57.14% | 14 | stage/parallel | Customer should be able to create an HCP cluster and manage ImageDigestMirrors |
Up to 50 failure patterns are loaded (minimum 1.00% impact), with 10 shown by default. Click column headers to re-sort.
Jump to the full Failure Patterns view for this window
No failure patterns available for this environment in the selected window.
Environment: PROD
E2E Jobs
13
Success Rate
0.00%
E2E success
Among runs that reached E2E execution, this shows how many completed successfully. Provision failures and 'Other' CI-infrastructure failures are excluded because those runs never reached the E2E step.n/a
Daily Run Outcomes
Successful runs
Provision failures
E2E failures
Other failures
| Pass rate | Runs | Date (UTC) | Suite | Test |
|---|---|---|---|---|
| 46.67% | 15 | prod/parallel | Customer should be able to forward control plane logs to a storage account and Event Hub via shoebox diagnostic settings | |
| 46.67% | 15 | prod/parallel | Customer should create a cluster with private KAS and verify API server is only reachable from VNet while ingress remains public | |
| 71.43% | 14 | prod/parallel | Customer should be able to delete a nodepool | |
| 73.33% | 15 | prod/parallel | Customer should be able to create a cluster and node pools with aggregated advanced features | |
| 80.00% | 15 | prod/parallel | Authorized CIDRs Connectivity should allow API access only from authorized VM IP |
Up to 50 failure patterns are loaded (minimum 1.00% impact), with 10 shown by default. Click column headers to re-sort.
Jump to the full Failure Patterns view for this window
No failure patterns available for this environment in the selected window.