CIHealth
<
Weekly: Sep 21 - Sep 27▾
Last 7 Days Weekly: Sep 21 - Sep 27 Sprint: Sep 14 - Sep 27
>
Env: ALL

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.
DEV95% - Post-good runs + Tide batches29422.79% (off track)-72.21pp+2.49pp76.43% (214/280)-18.31pp31.31% (67/214)-6.19pp
INT95% - All E2E job runs3265.62% (off track)-29.38pp+11.46ppn/an/a65.62% (21/32)-21.04pp
STG95% - All E2E job runs310.00% (off track)-95.00pp-5.00ppn/an/a0.00% (0/31)-10.00pp
PROD95% - All E2E job runs175.88% (off track)-89.12pp-13.04ppn/an/a5.88% (1/17)-21.04pp

Environment: DEV

E2E Jobs
685
Success Rate
15.77%
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.
73.69% (479/650)
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.
22.55% (108/479)
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.
294
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.79%
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.
76.43% (214/280)
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.
31.31% (67/214)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-21 UTC
92 runs
Successful runs: 3 of 92 runs (3.3%)
18%Provision failures: 17 of 92 runs (18.5%)
68%E2E failures: 63 of 92 runs (68.5%)
Other failures: 9 of 92 runs (9.8%)
2026-09-22 UTC
118 runs
14%Successful runs: 16 of 118 runs (13.6%)
Provision failures: 14 of 118 runs (11.9%)
72%E2E failures: 85 of 118 runs (72.0%)
Other failures: 3 of 118 runs (2.5%)
2026-09-23 UTC
97 runs
29%Successful runs: 28 of 97 runs (28.9%)
Provision failures: 8 of 97 runs (8.2%)
58%E2E failures: 56 of 97 runs (57.7%)
Other failures: 5 of 97 runs (5.2%)
2026-09-24 UTC
123 runs
24%Successful runs: 29 of 123 runs (23.6%)
16%Provision failures: 20 of 123 runs (16.3%)
58%E2E failures: 71 of 123 runs (57.7%)
Other failures: 3 of 123 runs (2.4%)
2026-09-25 UTC
149 runs
19%Successful runs: 28 of 149 runs (18.8%)
34%Provision failures: 51 of 149 runs (34.2%)
38%E2E failures: 57 of 149 runs (38.3%)
Other failures: 13 of 149 runs (8.7%)
2026-09-26 UTC
76 runs
Successful runs: 1 of 76 runs (1.3%)
79%Provision failures: 60 of 76 runs (78.9%)
E2E failures: 14 of 76 runs (18.4%)
Other failures: 1 of 76 runs (1.3%)
2026-09-27 UTC
30 runs
Successful runs: 3 of 30 runs (10.0%)
Provision failures: 1 of 30 runs (3.3%)
83%E2E failures: 25 of 30 runs (83.3%)
Other failures: 1 of 30 runs (3.3%)

Daily Run Outcomes for DEV Goal Basis (post-good + batches)

Successful runs (post-good + batches) Provision failures E2E failures Other failures
2026-09-21 UTC
49 runs
Successful runs (post-good + batches): 1 of 49 runs (2.0%)
18%Provision failures: 9 of 49 runs (18.4%)
69%E2E failures: 34 of 49 runs (69.4%)
Other failures: 5 of 49 runs (10.2%)
2026-09-22 UTC
48 runs
23%Successful runs (post-good + batches): 11 of 48 runs (22.9%)
Provision failures: 5 of 48 runs (10.4%)
65%E2E failures: 31 of 48 runs (64.6%)
Other failures: 1 of 48 runs (2.1%)
2026-09-23 UTC
43 runs
42%Successful runs (post-good + batches): 18 of 43 runs (41.9%)
Provision failures: 1 of 43 runs (2.3%)
47%E2E failures: 20 of 43 runs (46.5%)
Other failures: 4 of 43 runs (9.3%)
2026-09-24 UTC
47 runs
34%Successful runs (post-good + batches): 16 of 47 runs (34.0%)
Provision failures: 4 of 47 runs (8.5%)
55%E2E failures: 26 of 47 runs (55.3%)
Other failures: 1 of 47 runs (2.1%)
2026-09-25 UTC
61 runs
31%Successful runs (post-good + batches): 19 of 61 runs (31.1%)
31%Provision failures: 19 of 61 runs (31.1%)
34%E2E failures: 21 of 61 runs (34.4%)
Other failures: 2 of 61 runs (3.3%)
2026-09-26 UTC
36 runs
Successful runs (post-good + batches): 1 of 36 runs (2.8%)
78%Provision failures: 28 of 36 runs (77.8%)
E2E failures: 6 of 36 runs (16.7%)
Other failures: 1 of 36 runs (2.8%)
2026-09-27 UTC
10 runs
Successful runs (post-good + batches): 1 of 10 runs (10.0%)
90%E2E failures: 9 of 10 runs (90.0%)

Environment: INT

E2E Jobs
32
Success Rate
65.62%
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.
65.62% (21/32)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-21 UTC
5 runs
80%Successful runs: 4 of 5 runs (80.0%)
20%E2E failures: 1 of 5 runs (20.0%)
2026-09-22 UTC
3 runs
67%Successful runs: 2 of 3 runs (66.7%)
33%E2E failures: 1 of 3 runs (33.3%)
2026-09-23 UTC
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
2026-09-24 UTC
6 runs
83%Successful runs: 5 of 6 runs (83.3%)
17%E2E failures: 1 of 6 runs (16.7%)
2026-09-25 UTC
7 runs
43%Successful runs: 3 of 7 runs (42.9%)
57%E2E failures: 4 of 7 runs (57.1%)
2026-09-26 UTC
5 runs
80%Successful runs: 4 of 5 runs (80.0%)
20%E2E failures: 1 of 5 runs (20.0%)
2026-09-27 UTC
3 runs
67%Successful runs: 2 of 3 runs (66.7%)
33%E2E failures: 1 of 3 runs (33.3%)

Environment: STG

E2E Jobs
31
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.
0.00% (0/31)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-21 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-22 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-23 UTC
4 runs
100%E2E failures: 4 of 4 runs (100.0%)
2026-09-24 UTC
8 runs
100%E2E failures: 8 of 8 runs (100.0%)
2026-09-25 UTC
5 runs
100%E2E failures: 5 of 5 runs (100.0%)
2026-09-26 UTC
8 runs
100%E2E failures: 8 of 8 runs (100.0%)
2026-09-27 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)

Environment: PROD

E2E Jobs
17
Success Rate
5.88%
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.
5.88% (1/17)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-21 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-22 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2026-09-23 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-24 UTC
5 runs
100%E2E failures: 5 of 5 runs (100.0%)
2026-09-25 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-26 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-27 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)