CIHealth
<
Sprint: Oct 12 - Oct 25▾
Last 7 Days Weekly: Oct 19 - Oct 25 Sprint: Oct 12 - Oct 25
>
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 batches39640.91% (off track)-54.09pp+7.76pp91.82% (348/379)-2.54pp46.55% (162/348)+8.82pp
INT95% - All E2E job runs2913.79% (off track)-81.21pp-39.04ppn/an/a100.00% (4/4)+45.10pp
STG95% - All E2E job runs2722.22% (off track)-72.78pp+7.94ppn/an/a25.00% (6/24)+7.98pp
PROD95% - All E2E job runs9652.08% (off track)-42.92pp+18.15ppn/an/a54.95% (50/91)+19.76pp

Environment: DEV

E2E Jobs
995
Success Rate
29.55%
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.
88.00% (829/942)
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.
35.46% (294/829)
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.
396
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.
40.91%
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.
91.82% (348/379)
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.
46.55% (162/348)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-12 UTC
69 runs
23%Successful runs: 16 of 69 runs (23.2%)
Provision failures: 4 of 69 runs (5.8%)
70%E2E failures: 48 of 69 runs (69.6%)
Other failures: 1 of 69 runs (1.4%)
2026-10-13 UTC
81 runs
30%Successful runs: 24 of 81 runs (29.6%)
Provision failures: 3 of 81 runs (3.7%)
58%E2E failures: 47 of 81 runs (58.0%)
Other failures: 7 of 81 runs (8.6%)
2026-10-14 UTC
119 runs
20%Successful runs: 24 of 119 runs (20.2%)
Provision failures: 7 of 119 runs (5.9%)
68%E2E failures: 81 of 119 runs (68.1%)
Other failures: 7 of 119 runs (5.9%)
2026-10-15 UTC
134 runs
24%Successful runs: 32 of 134 runs (23.9%)
12%Provision failures: 16 of 134 runs (11.9%)
57%E2E failures: 77 of 134 runs (57.5%)
Other failures: 9 of 134 runs (6.7%)
2026-10-16 UTC
75 runs
36%Successful runs: 27 of 75 runs (36.0%)
21%Provision failures: 16 of 75 runs (21.3%)
43%E2E failures: 32 of 75 runs (42.7%)
2026-10-17 UTC
2 runs
E2E failures: 2 of 2 runs (100.0%)
2026-10-18 UTC
11 runs
Successful runs: 4 of 11 runs (36.4%)
Provision failures: 4 of 11 runs (36.4%)
E2E failures: 3 of 11 runs (27.3%)
2026-10-19 UTC
92 runs
18%Successful runs: 17 of 92 runs (18.5%)
16%Provision failures: 15 of 92 runs (16.3%)
58%E2E failures: 53 of 92 runs (57.6%)
Other failures: 7 of 92 runs (7.6%)
2026-10-20 UTC
93 runs
40%Successful runs: 37 of 93 runs (39.8%)
Provision failures: 10 of 93 runs (10.8%)
47%E2E failures: 44 of 93 runs (47.3%)
Other failures: 2 of 93 runs (2.2%)
2026-10-21 UTC
83 runs
37%Successful runs: 31 of 83 runs (37.3%)
Provision failures: 5 of 83 runs (6.0%)
54%E2E failures: 45 of 83 runs (54.2%)
Other failures: 2 of 83 runs (2.4%)
2026-10-22 UTC
99 runs
41%Successful runs: 41 of 99 runs (41.4%)
Provision failures: 12 of 99 runs (12.1%)
42%E2E failures: 42 of 99 runs (42.4%)
Other failures: 4 of 99 runs (4.0%)
2026-10-23 UTC
78 runs
32%Successful runs: 25 of 78 runs (32.1%)
Provision failures: 13 of 78 runs (16.7%)
44%E2E failures: 34 of 78 runs (43.6%)
Other failures: 6 of 78 runs (7.7%)
2026-10-24 UTC
42 runs
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%)

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

Successful runs (post-good + batches) Provision failures E2E failures Other failures
2026-10-12 UTC
21 runs
38%Successful runs (post-good + batches): 8 of 21 runs (38.1%)
Provision failures: 2 of 21 runs (9.5%)
52%E2E failures: 11 of 21 runs (52.4%)
2026-10-13 UTC
33 runs
33%Successful runs (post-good + batches): 11 of 33 runs (33.3%)
64%E2E failures: 21 of 33 runs (63.6%)
Other failures: 1 of 33 runs (3.0%)
2026-10-14 UTC
49 runs
24%Successful runs (post-good + batches): 12 of 49 runs (24.5%)
Provision failures: 2 of 49 runs (4.1%)
69%E2E failures: 34 of 49 runs (69.4%)
Other failures: 1 of 49 runs (2.0%)
2026-10-15 UTC
71 runs
31%Successful runs (post-good + batches): 22 of 71 runs (31.0%)
15%Provision failures: 11 of 71 runs (15.5%)
48%E2E failures: 34 of 71 runs (47.9%)
Other failures: 4 of 71 runs (5.6%)
2026-10-16 UTC
25 runs
60%Successful runs (post-good + batches): 15 of 25 runs (60.0%)
Provision failures: 3 of 25 runs (12.0%)
E2E failures: 7 of 25 runs (28.0%)
2026-10-17 UTC
1 run
E2E failures: 1 of 1 runs (100.0%)
2026-10-18 UTC
8 runs
Successful runs (post-good + batches): 4 of 8 runs (50.0%)
Provision failures: 1 of 8 runs (12.5%)
E2E failures: 3 of 8 runs (37.5%)
2026-10-19 UTC
24 runs
42%Successful runs (post-good + batches): 10 of 24 runs (41.7%)
Provision failures: 1 of 24 runs (4.2%)
50%E2E failures: 12 of 24 runs (50.0%)
Other failures: 1 of 24 runs (4.2%)
2026-10-20 UTC
44 runs
57%Successful runs (post-good + batches): 25 of 44 runs (56.8%)
Provision failures: 1 of 44 runs (2.3%)
41%E2E failures: 18 of 44 runs (40.9%)
2026-10-21 UTC
32 runs
34%Successful runs (post-good + batches): 11 of 32 runs (34.4%)
Provision failures: 1 of 32 runs (3.1%)
56%E2E failures: 18 of 32 runs (56.2%)
Other failures: 2 of 32 runs (6.2%)
2026-10-22 UTC
38 runs
53%Successful runs (post-good + batches): 20 of 38 runs (52.6%)
Provision failures: 4 of 38 runs (10.5%)
34%E2E failures: 13 of 38 runs (34.2%)
Other failures: 1 of 38 runs (2.6%)
2026-10-23 UTC
26 runs
50%Successful runs (post-good + batches): 13 of 26 runs (50.0%)
Provision failures: 3 of 26 runs (11.5%)
35%E2E failures: 9 of 26 runs (34.6%)
Other failures: 1 of 26 runs (3.8%)
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%)
Other failures: 6 of 21 runs (28.6%)
2026-10-25 UTC
3 runs
Successful runs (post-good + batches): 2 of 3 runs (66.7%)
Provision failures: 1 of 3 runs (33.3%)

Environment: INT

E2E Jobs
29
Success Rate
13.79%
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% (4/4)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-12 UTC
0 runs
No runs
2026-10-13 UTC
0 runs
No runs
2026-10-14 UTC
0 runs
No runs
2026-10-15 UTC
0 runs
No runs
2026-10-16 UTC
0 runs
No runs
2026-10-17 UTC
0 runs
No runs
2026-10-18 UTC
0 runs
No runs
2026-10-19 UTC
0 runs
No runs
2026-10-20 UTC
0 runs
No runs
2026-10-21 UTC
1 run
100%Other failures: 1 of 1 runs (100.0%)
2026-10-22 UTC
9 runs
22%Successful runs: 2 of 9 runs (22.2%)
78%Other failures: 7 of 9 runs (77.8%)
2026-10-23 UTC
6 runs
100%Other failures: 6 of 6 runs (100.0%)
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%)

Environment: STG

E2E Jobs
27
Success Rate
22.22%
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.
25.00% (6/24)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-12 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2026-10-13 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-14 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-15 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2026-10-16 UTC
1 run
100%E2E failures: 1 of 1 runs (100.0%)
2026-10-17 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-18 UTC
1 run
100%E2E failures: 1 of 1 runs (100.0%)
2026-10-19 UTC
2 runs
100%Other failures: 2 of 2 runs (100.0%)
2026-10-20 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%Other failures: 1 of 2 runs (50.0%)
2026-10-21 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2026-10-22 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-23 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
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%)

Environment: PROD

E2E Jobs
96
Success Rate
52.08%
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.
54.95% (50/91)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-12 UTC
17 runs
59%Successful runs: 10 of 17 runs (58.8%)
29%E2E failures: 5 of 17 runs (29.4%)
12%Other failures: 2 of 17 runs (11.8%)
2026-10-13 UTC
1 run
E2E failures: 1 of 1 runs (100.0%)
2026-10-14 UTC
3 runs
100%E2E failures: 3 of 3 runs (100.0%)
2026-10-15 UTC
11 runs
55%Successful runs: 6 of 11 runs (54.5%)
45%E2E failures: 5 of 11 runs (45.5%)
2026-10-16 UTC
1 run
E2E failures: 1 of 1 runs (100.0%)
2026-10-17 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-18 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-19 UTC
10 runs
80%Successful runs: 8 of 10 runs (80.0%)
20%E2E failures: 2 of 10 runs (20.0%)
2026-10-20 UTC
7 runs
57%Successful runs: 4 of 7 runs (57.1%)
43%E2E failures: 3 of 7 runs (42.9%)
2026-10-21 UTC
12 runs
75%Successful runs: 9 of 12 runs (75.0%)
25%E2E failures: 3 of 12 runs (25.0%)
2026-10-22 UTC
11 runs
45%Successful runs: 5 of 11 runs (45.5%)
36%E2E failures: 4 of 11 runs (36.4%)
18%Other failures: 2 of 11 runs (18.2%)
2026-10-23 UTC
14 runs
50%Successful runs: 7 of 14 runs (50.0%)
43%E2E failures: 6 of 14 runs (42.9%)
Other failures: 1 of 14 runs (7.1%)
2026-10-24 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-10-25 UTC
3 runs
Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)