CIHealth
<
Weekly: Sep 14 - Sep 20▾
Last 7 Days Weekly: Sep 14 - Sep 20 Sprint: Sep 14 - Sep 27
>
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 batches39920.30% (off track)-74.70pp-1.86pp94.74% (216/228)-5.26pp37.50% (81/216)-62.50pp
INT95% - All E2E job runs2454.17% (off track)-40.83pp-22.30ppn/an/a86.67% (13/15)-13.33pp
STG95% - All E2E job runs205.00% (off track)-90.00pp-7.50ppn/an/a10.00% (1/10)-90.00pp
PROD95% - All E2E job runs3718.92% (off track)-76.08pp+18.92ppn/an/a26.92% (7/26)n/a

Environment: DEV

E2E Jobs
728
Success Rate
16.62%
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.73% (362/399)
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.
33.43% (121/362)
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.
399
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.
20.30%
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.74% (216/228)
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.50% (81/216)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-14 UTC
80 runs
Successful runs: 7 of 80 runs (8.8%)
91%Other failures: 73 of 80 runs (91.2%)
2026-09-15 UTC
162 runs
20%Successful runs: 32 of 162 runs (19.8%)
80%Other failures: 130 of 162 runs (80.2%)
2026-09-16 UTC
144 runs
17%Successful runs: 24 of 144 runs (16.7%)
Provision failures: 19 of 144 runs (13.2%)
58%E2E failures: 83 of 144 runs (57.6%)
Other failures: 18 of 144 runs (12.5%)
2026-09-17 UTC
196 runs
10%Successful runs: 20 of 196 runs (10.2%)
Provision failures: 7 of 196 runs (3.6%)
38%E2E failures: 74 of 196 runs (37.8%)
48%Other failures: 95 of 196 runs (48.5%)
2026-09-18 UTC
84 runs
30%Successful runs: 25 of 84 runs (29.8%)
Provision failures: 7 of 84 runs (8.3%)
50%E2E failures: 42 of 84 runs (50.0%)
Other failures: 10 of 84 runs (11.9%)
2026-09-19 UTC
26 runs
Successful runs: 7 of 26 runs (26.9%)
Provision failures: 3 of 26 runs (11.5%)
E2E failures: 16 of 26 runs (61.5%)
2026-09-20 UTC
36 runs
Successful runs: 6 of 36 runs (16.7%)
Provision failures: 1 of 36 runs (2.8%)
72%E2E failures: 26 of 36 runs (72.2%)
Other failures: 3 of 36 runs (8.3%)

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

Successful runs (post-good + batches) Provision failures E2E failures Other failures
2026-09-14 UTC
35 runs
Successful runs (post-good + batches): 4 of 35 runs (11.4%)
89%Other failures: 31 of 35 runs (88.6%)
2026-09-15 UTC
73 runs
25%Successful runs (post-good + batches): 18 of 73 runs (24.7%)
75%Other failures: 55 of 73 runs (75.3%)
2026-09-16 UTC
67 runs
22%Successful runs (post-good + batches): 15 of 67 runs (22.4%)
Provision failures: 5 of 67 runs (7.5%)
55%E2E failures: 37 of 67 runs (55.2%)
Other failures: 10 of 67 runs (14.9%)
2026-09-17 UTC
123 runs
12%Successful runs (post-good + batches): 15 of 123 runs (12.2%)
Provision failures: 3 of 123 runs (2.4%)
33%E2E failures: 40 of 123 runs (32.5%)
53%Other failures: 65 of 123 runs (52.8%)
2026-09-18 UTC
52 runs
33%Successful runs (post-good + batches): 17 of 52 runs (32.7%)
Provision failures: 2 of 52 runs (3.8%)
50%E2E failures: 26 of 52 runs (50.0%)
Other failures: 7 of 52 runs (13.5%)
2026-09-19 UTC
19 runs
Successful runs (post-good + batches): 6 of 19 runs (31.6%)
Provision failures: 1 of 19 runs (5.3%)
E2E failures: 12 of 19 runs (63.2%)
2026-09-20 UTC
30 runs
Successful runs (post-good + batches): 6 of 30 runs (20.0%)
Provision failures: 1 of 30 runs (3.3%)
67%E2E failures: 20 of 30 runs (66.7%)
Other failures: 3 of 30 runs (10.0%)

Environment: INT

E2E Jobs
24
Success Rate
54.17%
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.
86.67% (13/15)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-14 UTC
4 runs
75%Successful runs: 3 of 4 runs (75.0%)
25%Other failures: 1 of 4 runs (25.0%)
2026-09-15 UTC
4 runs
100%Other failures: 4 of 4 runs (100.0%)
2026-09-16 UTC
4 runs
75%Successful runs: 3 of 4 runs (75.0%)
25%E2E failures: 1 of 4 runs (25.0%)
2026-09-17 UTC
8 runs
38%Successful runs: 3 of 8 runs (37.5%)
13%E2E failures: 1 of 8 runs (12.5%)
50%Other failures: 4 of 8 runs (50.0%)
2026-09-18 UTC
3 runs
100%Successful runs: 3 of 3 runs (100.0%)
2026-09-19 UTC
1 run
100%Successful runs: 1 of 1 runs (100.0%)
2026-09-20 UTC
0 runs
No runs

Environment: STG

E2E Jobs
20
Success Rate
5.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.
10.00% (1/10)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-14 UTC
5 runs
100%Other failures: 5 of 5 runs (100.0%)
2026-09-15 UTC
3 runs
100%Other failures: 3 of 3 runs (100.0%)
2026-09-16 UTC
2 runs
50%E2E failures: 1 of 2 runs (50.0%)
50%Other failures: 1 of 2 runs (50.0%)
2026-09-17 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-09-18 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-19 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2026-09-20 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)

Environment: PROD

E2E Jobs
37
Success Rate
18.92%
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.
26.92% (7/26)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-09-14 UTC
2 runs
100%Other failures: 2 of 2 runs (100.0%)
2026-09-15 UTC
4 runs
100%Other failures: 4 of 4 runs (100.0%)
2026-09-16 UTC
5 runs
40%E2E failures: 2 of 5 runs (40.0%)
60%Other failures: 3 of 5 runs (60.0%)
2026-09-17 UTC
5 runs
60%E2E failures: 3 of 5 runs (60.0%)
40%Other failures: 2 of 5 runs (40.0%)
2026-09-18 UTC
15 runs
40%Successful runs: 6 of 15 runs (40.0%)
60%E2E failures: 9 of 15 runs (60.0%)
2026-09-19 UTC
4 runs
Successful runs: 1 of 4 runs (25.0%)
75%E2E failures: 3 of 4 runs (75.0%)
2026-09-20 UTC
2 runs
100%E2E failures: 2 of 2 runs (100.0%)