CIHealth
<
Last 7 Days▾
Last 7 Days Weekly: Oct 26 - Nov 1 Sprint: Oct 26 - Nov 8
>
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 batches16943.79% (off track)-51.21pp-4.19pp92.11% (140/152)-1.35pp52.86% (74/140)-0.01pp
INT95% - All E2E job runs3850.00% (off track)-45.00pp+37.50ppn/an/a100.00% (19/19)+0.00pp
STG95% - All E2E job runs2839.29% (off track)-55.71pp+23.90ppn/an/a61.11% (11/18)+41.11pp
PROD95% - All E2E job runs7764.94% (off track)-30.06pp+8.04ppn/an/a70.42% (50/71)+10.42pp

Environment: DEV

E2E Jobs
414
Success Rate
33.09%
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.
90.22% (323/358)
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.
42.41% (137/323)
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.
169
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.
43.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.
92.11% (140/152)
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.
52.86% (74/140)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-24 UTC
42 runs
31%Successful runs: 13 of 42 runs (31.0%)
Provision failures: 3 of 42 runs (7.1%)
45%E2E failures: 19 of 42 runs (45.2%)
Other failures: 7 of 42 runs (16.7%)
2026-10-25 UTC
17 runs
Successful runs: 3 of 17 runs (17.6%)
Provision failures: 5 of 17 runs (29.4%)
E2E failures: 8 of 17 runs (47.1%)
Other failures: 1 of 17 runs (5.9%)
2026-10-26 UTC
48 runs
54%Successful runs: 26 of 48 runs (54.2%)
Provision failures: 2 of 48 runs (4.2%)
40%E2E failures: 19 of 48 runs (39.6%)
Other failures: 1 of 48 runs (2.1%)
2026-10-27 UTC
113 runs
30%Successful runs: 34 of 113 runs (30.1%)
Provision failures: 11 of 113 runs (9.7%)
55%E2E failures: 62 of 113 runs (54.9%)
Other failures: 6 of 113 runs (5.3%)
2026-10-28 UTC
90 runs
31%Successful runs: 28 of 90 runs (31.1%)
Provision failures: 7 of 90 runs (7.8%)
46%E2E failures: 41 of 90 runs (45.6%)
16%Other failures: 14 of 90 runs (15.6%)
2026-10-29 UTC
104 runs
32%Successful runs: 33 of 104 runs (31.7%)
Provision failures: 7 of 104 runs (6.7%)
36%E2E failures: 37 of 104 runs (35.6%)
26%Other failures: 27 of 104 runs (26.0%)
2026-10-30 UTC
0 runs
No runs

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

Successful runs (post-good + batches) Provision failures E2E failures Other failures
2026-10-24 UTC
21 runs
43%Successful runs (post-good + batches): 9 of 21 runs (42.9%)
Provision failures: 1 of 21 runs (4.8%)
E2E failures: 5 of 21 runs (23.8%)
29%Other failures: 6 of 21 runs (28.6%)
2026-10-25 UTC
2 runs
Successful runs (post-good + batches): 1 of 2 runs (50.0%)
Provision failures: 1 of 2 runs (50.0%)
2026-10-26 UTC
18 runs
67%Successful runs (post-good + batches): 12 of 18 runs (66.7%)
Provision failures: 1 of 18 runs (5.6%)
E2E failures: 5 of 18 runs (27.8%)
2026-10-27 UTC
58 runs
34%Successful runs (post-good + batches): 20 of 58 runs (34.5%)
10%Provision failures: 6 of 58 runs (10.3%)
52%E2E failures: 30 of 58 runs (51.7%)
Other failures: 2 of 58 runs (3.4%)
2026-10-28 UTC
49 runs
45%Successful runs (post-good + batches): 22 of 49 runs (44.9%)
Provision failures: 2 of 49 runs (4.1%)
39%E2E failures: 19 of 49 runs (38.8%)
12%Other failures: 6 of 49 runs (12.2%)
2026-10-29 UTC
21 runs
48%Successful runs (post-good + batches): 10 of 21 runs (47.6%)
Provision failures: 1 of 21 runs (4.8%)
33%E2E failures: 7 of 21 runs (33.3%)
Other failures: 3 of 21 runs (14.3%)
2026-10-30 UTC
0 runs
No runs

Environment: INT

E2E Jobs
38
Success Rate
50.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.
100.00% (19/19)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-24 UTC
7 runs
100%Other failures: 7 of 7 runs (100.0%)
2026-10-25 UTC
6 runs
33%Successful runs: 2 of 6 runs (33.3%)
67%Other failures: 4 of 6 runs (66.7%)
2026-10-26 UTC
4 runs
75%Successful runs: 3 of 4 runs (75.0%)
Other failures: 1 of 4 runs (25.0%)
2026-10-27 UTC
6 runs
50%Successful runs: 3 of 6 runs (50.0%)
50%Other failures: 3 of 6 runs (50.0%)
2026-10-28 UTC
5 runs
100%Successful runs: 5 of 5 runs (100.0%)
2026-10-29 UTC
10 runs
60%Successful runs: 6 of 10 runs (60.0%)
40%Other failures: 4 of 10 runs (40.0%)
2026-10-30 UTC
0 runs
No runs

Environment: STG

E2E Jobs
28
Success Rate
39.29%
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.
61.11% (11/18)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-24 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-25 UTC
3 runs
67%Successful runs: 2 of 3 runs (66.7%)
33%E2E failures: 1 of 3 runs (33.3%)
2026-10-26 UTC
5 runs
40%Successful runs: 2 of 5 runs (40.0%)
20%E2E failures: 1 of 5 runs (20.0%)
40%Other failures: 2 of 5 runs (40.0%)
2026-10-27 UTC
6 runs
50%Successful runs: 3 of 6 runs (50.0%)
33%E2E failures: 2 of 6 runs (33.3%)
17%Other failures: 1 of 6 runs (16.7%)
2026-10-28 UTC
6 runs
33%Successful runs: 2 of 6 runs (33.3%)
17%E2E failures: 1 of 6 runs (16.7%)
50%Other failures: 3 of 6 runs (50.0%)
2026-10-29 UTC
6 runs
33%Successful runs: 2 of 6 runs (33.3%)
67%Other failures: 4 of 6 runs (66.7%)
2026-10-30 UTC
0 runs
No runs

Environment: PROD

E2E Jobs
77
Success Rate
64.94%
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.
70.42% (50/71)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-24 UTC
2 runs
E2E failures: 2 of 2 runs (100.0%)
2026-10-25 UTC
3 runs
Successful runs: 1 of 3 runs (33.3%)
E2E failures: 2 of 3 runs (66.7%)
2026-10-26 UTC
14 runs
57%Successful runs: 8 of 14 runs (57.1%)
E2E failures: 2 of 14 runs (14.3%)
29%Other failures: 4 of 14 runs (28.6%)
2026-10-27 UTC
25 runs
80%Successful runs: 20 of 25 runs (80.0%)
20%E2E failures: 5 of 25 runs (20.0%)
2026-10-28 UTC
12 runs
67%Successful runs: 8 of 12 runs (66.7%)
33%E2E failures: 4 of 12 runs (33.3%)
2026-10-29 UTC
21 runs
62%Successful runs: 13 of 21 runs (61.9%)
29%E2E failures: 6 of 21 runs (28.6%)
Other failures: 2 of 21 runs (9.5%)
2026-10-30 UTC
0 runs
No runs