CIHealth
<
Weekly: Sep 28 - Oct 4▾
Last 7 Days Weekly: Sep 28 - Oct 4 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 batches21535.81% (off track)-59.19pp+13.02pp94.06% (190/202)+17.63pp40.53% (77/190)+9.22pp
INT95% - All E2E job runs3053.33% (off track)-41.67pp-12.29ppn/an/a57.14% (16/28)-8.48pp
STG95% - All E2E job runs2910.34% (off track)-84.66pp+10.34ppn/an/a11.54% (3/26)+11.54pp
PROD95% - All E2E job runs7636.84% (off track)-58.16pp+30.96ppn/an/a36.84% (28/76)+30.96pp

Environment: DEV

E2E Jobs
523
Success Rate
27.92%
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.
92.06% (452/491)
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.
32.30% (146/452)
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.
215
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.
35.81%
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.06% (190/202)
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.
40.53% (77/190)

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%)

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%)

Environment: INT

E2E Jobs
30
Success Rate
53.33%
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.
57.14% (16/28)

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%)

Environment: STG

E2E Jobs
29
Success Rate
10.34%
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.
11.54% (3/26)

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%)

Environment: PROD

E2E Jobs
76
Success Rate
36.84%
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.
36.84% (28/76)

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%)