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 | 0 | n/a (insufficient data) | n/a | n/a | n/a | n/a | n/a | n/a |
| INT | 95% - All E2E job runs | 0 | n/a (insufficient data) | n/a | n/a | n/a | n/a | n/a | n/a |
| STG | 95% - All E2E job runs | 0 | n/a (insufficient data) | n/a | n/a | n/a | n/a | n/a | n/a |
| PROD | 95% - All E2E job runs | 0 | n/a (insufficient data) | n/a | n/a | n/a | n/a | n/a | n/a |
Environment: DEV
E2E Jobs
0
Success Rate
0.00%
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.n/a
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
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.0
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.0.00%
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.n/a
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.n/a
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
| Pass rate | Runs | Date (UTC) | Suite | Test |
|---|---|---|---|---|
| 57.89% | 19 | rp-api-compat-all/parallel | Engineering should be able to retrieve expected metrics from the /metrics endpoint | |
| 74.44% | 313 | step graph | Run pipeline step Microsoft.Azure.ARO.HCP.Region/regional/infra | |
| 94.69% | 113 | rp-api-compat-all/parallel | Customer should not be able to perform various invalid operations on cluster resources |
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
0
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 |
|---|---|---|---|---|
| 69.70% | 33 | integration/parallel | Customer should be able to create an HCP cluster | |
| 69.70% | 33 | integration/parallel | Customer should be able to create an HCP cluster with custom autoscaling | |
| 72.73% | 33 | integration/parallel | Customer should be able to create an HCP cluster and custom node pool osDisk size | |
| 72.73% | 33 | integration/parallel | Customer should be able to create an HCP cluster with back-level version 4.19 | |
| 72.73% | 33 | integration/parallel | Customer should be able to create node pools with ARM64-based VMs |
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
0
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 |
|---|---|---|---|---|
| 56.25% | 16 | stage/parallel | Authorized CIDRs Connectivity should allow API access only from authorized VM IP | |
| 56.25% | 16 | stage/parallel | Customer should be able to create an HCP cluster and manage pull secrets | |
| 56.25% | 16 | stage/parallel | Customer should be able to create node pools with ARM64-based VMs | |
| 62.50% | 16 | stage/parallel | Customer should be able to create a cluster with an external auth config and get the external auth config | |
| 62.50% | 16 | stage/parallel | Customer should be able to create a cluster with default autoscaling and a nodepool with autoscaling enabled |
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
0
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 |
|---|---|---|---|---|
| 66.67% | 24 | prod/parallel | Authorized CIDRs Connectivity should allow API access only from authorized VM IP | |
| 66.67% | 24 | prod/parallel | Customer should be able to create a cluster with an external auth config and get the external auth config | |
| 66.67% | 24 | prod/parallel | Customer should be able to create an HCP cluster and custom node pool osDisk size | |
| 66.67% | 24 | prod/parallel | Customer should be able to create an HCP cluster and manage pull secrets | |
| 66.67% | 24 | prod/parallel | Customer should create an HCP cluster and validate TLS certificates |
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.