CIHealth
<
Sprint: Sep 28 - Oct 11▾
Last 7 Days Weekly: Oct 5 - Oct 11 Sprint: Sep 28 - Oct 11
>
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 batches36233.15% (off track)-61.85pp+11.79pp94.36% (318/337)+9.72pp37.74% (120/318)+3.32pp
INT95% - All E2E job runs5352.83% (off track)-42.17pp-7.88ppn/an/a54.90% (28/51)-17.44pp
STG95% - All E2E job runs5614.29% (off track)-80.71pp+12.32ppn/an/a17.02% (8/47)+14.58pp
PROD95% - All E2E job runs11233.93% (off track)-61.07pp+19.11ppn/an/a35.19% (38/108)+16.58pp

Environment: DEV

E2E Jobs
930
Success Rate
24.41%
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.
91.94% (798/868)
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.
28.45% (227/798)
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.
362
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.
33.15%
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.
94.36% (318/337)
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.
37.74% (120/318)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-28 UTC
114 runs
15%Successful runs: 17 of 114 runs (14.9%)
11%Provision failures: 13 of 114 runs (11.4%)
65%E2E failures: 74 of 114 runs (64.9%)
Other failures: 10 of 114 runs (8.8%)
2026-09-29 UTC
107 runs
18%Successful runs: 19 of 107 runs (17.8%)
Provision failures: 9 of 107 runs (8.4%)
69%E2E failures: 74 of 107 runs (69.2%)
Other failures: 5 of 107 runs (4.7%)
2026-09-30 UTC
98 runs
47%Successful runs: 46 of 98 runs (46.9%)
Provision failures: 7 of 98 runs (7.1%)
42%E2E failures: 41 of 98 runs (41.8%)
Other failures: 4 of 98 runs (4.1%)
2026-10-01 UTC
86 runs
38%Successful runs: 33 of 86 runs (38.4%)
Provision failures: 6 of 86 runs (7.0%)
43%E2E failures: 37 of 86 runs (43.0%)
Other failures: 10 of 86 runs (11.6%)
2026-10-02 UTC
66 runs
27%Successful runs: 18 of 66 runs (27.3%)
Provision failures: 2 of 66 runs (3.0%)
67%E2E failures: 44 of 66 runs (66.7%)
Other failures: 2 of 66 runs (3.0%)
2026-10-03 UTC
39 runs
31%Successful runs: 12 of 39 runs (30.8%)
Provision failures: 2 of 39 runs (5.1%)
62%E2E failures: 24 of 39 runs (61.5%)
Other failures: 1 of 39 runs (2.6%)
2026-10-04 UTC
13 runs
Successful runs: 1 of 13 runs (7.7%)
92%E2E failures: 12 of 13 runs (92.3%)
2026-10-05 UTC
77 runs
Successful runs: 10 of 77 runs (13.0%)
Provision failures: 6 of 77 runs (7.8%)
73%E2E failures: 56 of 77 runs (72.7%)
Other failures: 5 of 77 runs (6.5%)
2026-10-06 UTC
85 runs
14%Successful runs: 12 of 85 runs (14.1%)
Provision failures: 8 of 85 runs (9.4%)
67%E2E failures: 57 of 85 runs (67.1%)
Other failures: 8 of 85 runs (9.4%)
2026-10-07 UTC
71 runs
Successful runs: 10 of 71 runs (14.1%)
Provision failures: 5 of 71 runs (7.0%)
70%E2E failures: 50 of 71 runs (70.4%)
Other failures: 6 of 71 runs (8.5%)
2026-10-08 UTC
91 runs
27%Successful runs: 25 of 91 runs (27.5%)
Provision failures: 6 of 91 runs (6.6%)
59%E2E failures: 54 of 91 runs (59.3%)
Other failures: 6 of 91 runs (6.6%)
2026-10-09 UTC
59 runs
29%Successful runs: 17 of 59 runs (28.8%)
Provision failures: 6 of 59 runs (10.2%)
54%E2E failures: 32 of 59 runs (54.2%)
Other failures: 4 of 59 runs (6.8%)
2026-10-10 UTC
14 runs
Successful runs: 7 of 14 runs (50.0%)
E2E failures: 7 of 14 runs (50.0%)
2026-10-11 UTC
10 runs
E2E failures: 9 of 10 runs (90.0%)
Other failures: 1 of 10 runs (10.0%)

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

Successful runs (post-good + batches) Provision failures E2E failures Other failures
2026-09-28 UTC
43 runs
23%Successful runs (post-good + batches): 10 of 43 runs (23.3%)
12%Provision failures: 5 of 43 runs (11.6%)
60%E2E failures: 26 of 43 runs (60.5%)
Other failures: 2 of 43 runs (4.7%)
2026-09-29 UTC
44 runs
25%Successful runs (post-good + batches): 11 of 44 runs (25.0%)
Provision failures: 1 of 44 runs (2.3%)
73%E2E failures: 32 of 44 runs (72.7%)
2026-09-30 UTC
39 runs
59%Successful runs (post-good + batches): 23 of 39 runs (59.0%)
Provision failures: 1 of 39 runs (2.6%)
33%E2E failures: 13 of 39 runs (33.3%)
Other failures: 2 of 39 runs (5.1%)
2026-10-01 UTC
39 runs
49%Successful runs (post-good + batches): 19 of 39 runs (48.7%)
Provision failures: 3 of 39 runs (7.7%)
28%E2E failures: 11 of 39 runs (28.2%)
15%Other failures: 6 of 39 runs (15.4%)
2026-10-02 UTC
26 runs
31%Successful runs (post-good + batches): 8 of 26 runs (30.8%)
62%E2E failures: 16 of 26 runs (61.5%)
Other failures: 2 of 26 runs (7.7%)
2026-10-03 UTC
19 runs
32%Successful runs (post-good + batches): 6 of 19 runs (31.6%)
Provision failures: 2 of 19 runs (10.5%)
53%E2E failures: 10 of 19 runs (52.6%)
Other failures: 1 of 19 runs (5.3%)
2026-10-04 UTC
5 runs
100%E2E failures: 5 of 5 runs (100.0%)
2026-10-05 UTC
19 runs
26%Successful runs (post-good + batches): 5 of 19 runs (26.3%)
63%E2E failures: 12 of 19 runs (63.2%)
Other failures: 2 of 19 runs (10.5%)
2026-10-06 UTC
21 runs
43%Successful runs (post-good + batches): 9 of 21 runs (42.9%)
48%E2E failures: 10 of 21 runs (47.6%)
Other failures: 2 of 21 runs (9.5%)
2026-10-07 UTC
23 runs
Successful runs (post-good + batches): 4 of 23 runs (17.4%)
Provision failures: 2 of 23 runs (8.7%)
61%E2E failures: 14 of 23 runs (60.9%)
Other failures: 3 of 23 runs (13.0%)
2026-10-08 UTC
44 runs
30%Successful runs (post-good + batches): 13 of 44 runs (29.5%)
Provision failures: 4 of 44 runs (9.1%)
57%E2E failures: 25 of 44 runs (56.8%)
Other failures: 2 of 44 runs (4.5%)
2026-10-09 UTC
23 runs
30%Successful runs (post-good + batches): 7 of 23 runs (30.4%)
Provision failures: 1 of 23 runs (4.3%)
57%E2E failures: 13 of 23 runs (56.5%)
Other failures: 2 of 23 runs (8.7%)
2026-10-10 UTC
11 runs
45%Successful runs (post-good + batches): 5 of 11 runs (45.5%)
55%E2E failures: 6 of 11 runs (54.5%)
2026-10-11 UTC
6 runs
83%E2E failures: 5 of 6 runs (83.3%)
Other failures: 1 of 6 runs (16.7%)

Environment: INT

E2E Jobs
53
Success Rate
52.83%
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.90% (28/51)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-28 UTC
3 runs
67%Successful runs: 2 of 3 runs (66.7%)
33%E2E failures: 1 of 3 runs (33.3%)
2026-09-29 UTC
6 runs
33%Successful runs: 2 of 6 runs (33.3%)
67%E2E failures: 4 of 6 runs (66.7%)
2026-09-30 UTC
8 runs
38%Successful runs: 3 of 8 runs (37.5%)
38%E2E failures: 3 of 8 runs (37.5%)
25%Other failures: 2 of 8 runs (25.0%)
2026-10-01 UTC
6 runs
33%Successful runs: 2 of 6 runs (33.3%)
67%E2E failures: 4 of 6 runs (66.7%)
2026-10-02 UTC
5 runs
100%Successful runs: 5 of 5 runs (100.0%)
2026-10-03 UTC
0 runs
No runs
2026-10-04 UTC
2 runs
100%Successful runs: 2 of 2 runs (100.0%)
2026-10-05 UTC
6 runs
50%Successful runs: 3 of 6 runs (50.0%)
50%E2E failures: 3 of 6 runs (50.0%)
2026-10-06 UTC
7 runs
29%Successful runs: 2 of 7 runs (28.6%)
71%E2E failures: 5 of 7 runs (71.4%)
2026-10-07 UTC
4 runs
100%Successful runs: 4 of 4 runs (100.0%)
2026-10-08 UTC
6 runs
50%Successful runs: 3 of 6 runs (50.0%)
50%E2E failures: 3 of 6 runs (50.0%)
2026-10-09 UTC
0 runs
No runs
2026-10-10 UTC
0 runs
No runs
2026-10-11 UTC
0 runs
No runs

Environment: STG

E2E Jobs
56
Success Rate
14.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.
17.02% (8/47)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-28 UTC
4 runs
50%Successful runs: 2 of 4 runs (50.0%)
50%E2E failures: 2 of 4 runs (50.0%)
2026-09-29 UTC
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
2026-09-30 UTC
5 runs
100%E2E failures: 5 of 5 runs (100.0%)
2026-10-01 UTC
4 runs
75%E2E failures: 3 of 4 runs (75.0%)
25%Other failures: 1 of 4 runs (25.0%)
2026-10-02 UTC
6 runs
100%E2E failures: 6 of 6 runs (100.0%)
2026-10-03 UTC
4 runs
75%E2E failures: 3 of 4 runs (75.0%)
25%Other failures: 1 of 4 runs (25.0%)
2026-10-04 UTC
3 runs
67%E2E failures: 2 of 3 runs (66.7%)
33%Other failures: 1 of 3 runs (33.3%)
2026-10-05 UTC
4 runs
75%E2E failures: 3 of 4 runs (75.0%)
25%Other failures: 1 of 4 runs (25.0%)
2026-10-06 UTC
5 runs
40%E2E failures: 2 of 5 runs (40.0%)
60%Other failures: 3 of 5 runs (60.0%)
2026-10-07 UTC
6 runs
83%E2E failures: 5 of 6 runs (83.3%)
17%Other failures: 1 of 6 runs (16.7%)
2026-10-08 UTC
4 runs
25%Successful runs: 1 of 4 runs (25.0%)
50%E2E failures: 2 of 4 runs (50.0%)
25%Other failures: 1 of 4 runs (25.0%)
2026-10-09 UTC
4 runs
50%Successful runs: 2 of 4 runs (50.0%)
50%E2E failures: 2 of 4 runs (50.0%)
2026-10-10 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2026-10-11 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)

Environment: PROD

E2E Jobs
112
Success Rate
33.93%
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.19% (38/108)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-28 UTC
13 runs
46%Successful runs: 6 of 13 runs (46.2%)
54%E2E failures: 7 of 13 runs (53.8%)
2026-09-29 UTC
7 runs
Successful runs: 1 of 7 runs (14.3%)
86%E2E failures: 6 of 7 runs (85.7%)
2026-09-30 UTC
3 runs
Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
2026-10-01 UTC
12 runs
50%Successful runs: 6 of 12 runs (50.0%)
50%E2E failures: 6 of 12 runs (50.0%)
2026-10-02 UTC
16 runs
44%Successful runs: 7 of 16 runs (43.8%)
56%E2E failures: 9 of 16 runs (56.2%)
2026-10-03 UTC
6 runs
33%Successful runs: 2 of 6 runs (33.3%)
67%E2E failures: 4 of 6 runs (66.7%)
2026-10-04 UTC
19 runs
26%Successful runs: 5 of 19 runs (26.3%)
74%E2E failures: 14 of 19 runs (73.7%)
2026-10-05 UTC
5 runs
40%Successful runs: 2 of 5 runs (40.0%)
60%E2E failures: 3 of 5 runs (60.0%)
2026-10-06 UTC
3 runs
100%E2E failures: 3 of 3 runs (100.0%)
2026-10-07 UTC
7 runs
86%E2E failures: 6 of 7 runs (85.7%)
Other failures: 1 of 7 runs (14.3%)
2026-10-08 UTC
7 runs
Successful runs: 1 of 7 runs (14.3%)
71%E2E failures: 5 of 7 runs (71.4%)
Other failures: 1 of 7 runs (14.3%)
2026-10-09 UTC
9 runs
56%Successful runs: 5 of 9 runs (55.6%)
22%E2E failures: 2 of 9 runs (22.2%)
22%Other failures: 2 of 9 runs (22.2%)
2026-10-10 UTC
2 runs
Successful runs: 1 of 2 runs (50.0%)
E2E failures: 1 of 2 runs (50.0%)
2026-10-11 UTC
3 runs
Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)