CIHealth
<
Weekly: Oct 26 - Nov 1▾
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 batches10146.53% (off track)-48.47pp-0.78pp91.67% (88/96)-1.48pp53.41% (47/88)-0.58pp
INT95% - All E2E job runs1573.33% (off track)-21.67pp+59.54ppn/an/a100.00% (11/11)+0.00pp
STG95% - All E2E job runs1442.86% (off track)-52.14pp+16.19ppn/an/a60.00% (6/10)+26.67pp
PROD95% - All E2E job runs4669.57% (off track)-25.43pp+11.94ppn/an/a76.19% (32/42)+15.48pp

Environment: DEV

E2E Jobs
235
Success Rate
35.32%
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.13% (199/216)
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.
41.71% (83/199)
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.
101
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.
46.53%
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.67% (88/96)
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.
53.41% (47/88)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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
74 runs
31%Successful runs: 23 of 74 runs (31.1%)
Provision failures: 4 of 74 runs (5.4%)
47%E2E failures: 35 of 74 runs (47.3%)
16%Other failures: 12 of 74 runs (16.2%)
2026-10-29 UTC
0 runs
No runs
2026-10-30 UTC
0 runs
No runs
2026-10-31 UTC
0 runs
No runs
2026-11-01 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-26 UTC
17 runs
65%Successful runs (post-good + batches): 11 of 17 runs (64.7%)
Provision failures: 1 of 17 runs (5.9%)
E2E failures: 5 of 17 runs (29.4%)
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
26 runs
62%Successful runs (post-good + batches): 16 of 26 runs (61.5%)
Provision failures: 1 of 26 runs (3.8%)
23%E2E failures: 6 of 26 runs (23.1%)
Other failures: 3 of 26 runs (11.5%)
2026-10-29 UTC
0 runs
No runs
2026-10-30 UTC
0 runs
No runs
2026-10-31 UTC
0 runs
No runs
2026-11-01 UTC
0 runs
No runs

Environment: INT

E2E Jobs
15
Success Rate
73.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.
100.00% (11/11)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-10-26 UTC
4 runs
75%Successful runs: 3 of 4 runs (75.0%)
25%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
0 runs
No runs
2026-10-30 UTC
0 runs
No runs
2026-10-31 UTC
0 runs
No runs
2026-11-01 UTC
0 runs
No runs

Environment: STG

E2E Jobs
14
Success Rate
42.86%
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.
60.00% (6/10)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
33%E2E failures: 1 of 3 runs (33.3%)
33%Other failures: 1 of 3 runs (33.3%)
2026-10-29 UTC
0 runs
No runs
2026-10-30 UTC
0 runs
No runs
2026-10-31 UTC
0 runs
No runs
2026-11-01 UTC
0 runs
No runs

Environment: PROD

E2E Jobs
46
Success Rate
69.57%
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.
76.19% (32/42)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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
7 runs
57%Successful runs: 4 of 7 runs (57.1%)
43%E2E failures: 3 of 7 runs (42.9%)
2026-10-29 UTC
0 runs
No runs
2026-10-30 UTC
0 runs
No runs
2026-10-31 UTC
0 runs
No runs
2026-11-01 UTC
0 runs
No runs