CIHealth
<
Last 7 Days▾
Last 7 Days Weekly: Nov 9 - Nov 15 Sprint: Nov 9 - Nov 22
>
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 batches10650.94% (off track)-44.06pp+8.89pp86.27% (88/102)-6.85pp61.36% (54/88)+10.23pp
INT95% - All E2E job runs2556.00% (off track)-39.00pp-24.95ppn/an/a93.33% (14/15)-6.67pp
STG95% - All E2E job runs2171.43% (off track)-23.57pp+38.10ppn/an/a75.00% (15/20)+0.00pp
PROD95% - All E2E job runs10236.27% (off track)-58.73pp-23.73ppn/an/a37.00% (37/100)-32.64pp

Environment: DEV

E2E Jobs
262
Success Rate
40.84%
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.
83.54% (203/243)
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.
52.71% (107/203)
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.
106
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.
50.94%
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.
86.27% (88/102)
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.
61.36% (54/88)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-11-04 UTC
70 runs
37%Successful runs: 26 of 70 runs (37.1%)
Provision failures: 7 of 70 runs (10.0%)
41%E2E failures: 29 of 70 runs (41.4%)
11%Other failures: 8 of 70 runs (11.4%)
2026-11-05 UTC
56 runs
45%Successful runs: 25 of 56 runs (44.6%)
14%Provision failures: 8 of 56 runs (14.3%)
30%E2E failures: 17 of 56 runs (30.4%)
Other failures: 6 of 56 runs (10.7%)
2026-11-06 UTC
68 runs
35%Successful runs: 24 of 68 runs (35.3%)
16%Provision failures: 11 of 68 runs (16.2%)
43%E2E failures: 29 of 68 runs (42.6%)
Other failures: 4 of 68 runs (5.9%)
2026-11-07 UTC
3 runs
Successful runs: 1 of 3 runs (33.3%)
Provision failures: 1 of 3 runs (33.3%)
E2E failures: 1 of 3 runs (33.3%)
2026-11-08 UTC
15 runs
Successful runs: 4 of 15 runs (26.7%)
Provision failures: 2 of 15 runs (13.3%)
53%E2E failures: 8 of 15 runs (53.3%)
Other failures: 1 of 15 runs (6.7%)
2026-11-09 UTC
50 runs
54%Successful runs: 27 of 50 runs (54.0%)
22%Provision failures: 11 of 50 runs (22.0%)
24%E2E failures: 12 of 50 runs (24.0%)
2026-11-10 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-11-04 UTC
27 runs
44%Successful runs (post-good + batches): 12 of 27 runs (44.4%)
Provision failures: 2 of 27 runs (7.4%)
41%E2E failures: 11 of 27 runs (40.7%)
Other failures: 2 of 27 runs (7.4%)
2026-11-05 UTC
21 runs
62%Successful runs (post-good + batches): 13 of 21 runs (61.9%)
Provision failures: 2 of 21 runs (9.5%)
24%E2E failures: 5 of 21 runs (23.8%)
Other failures: 1 of 21 runs (4.8%)
2026-11-06 UTC
28 runs
43%Successful runs (post-good + batches): 12 of 28 runs (42.9%)
25%Provision failures: 7 of 28 runs (25.0%)
29%E2E failures: 8 of 28 runs (28.6%)
Other failures: 1 of 28 runs (3.6%)
2026-11-07 UTC
0 runs
No runs
2026-11-08 UTC
6 runs
67%Successful runs (post-good + batches): 4 of 6 runs (66.7%)
E2E failures: 2 of 6 runs (33.3%)
2026-11-09 UTC
24 runs
54%Successful runs (post-good + batches): 13 of 24 runs (54.2%)
13%Provision failures: 3 of 24 runs (12.5%)
33%E2E failures: 8 of 24 runs (33.3%)
2026-11-10 UTC
0 runs
No runs

Environment: INT

E2E Jobs
25
Success Rate
56.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.
93.33% (14/15)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-11-04 UTC
8 runs
25%Successful runs: 2 of 8 runs (25.0%)
13%E2E failures: 1 of 8 runs (12.5%)
63%Other failures: 5 of 8 runs (62.5%)
2026-11-05 UTC
8 runs
88%Successful runs: 7 of 8 runs (87.5%)
13%Other failures: 1 of 8 runs (12.5%)
2026-11-06 UTC
6 runs
67%Successful runs: 4 of 6 runs (66.7%)
33%Other failures: 2 of 6 runs (33.3%)
2026-11-07 UTC
0 runs
No runs
2026-11-08 UTC
0 runs
No runs
2026-11-09 UTC
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%Other failures: 2 of 3 runs (66.7%)
2026-11-10 UTC
0 runs
No runs

Environment: STG

E2E Jobs
21
Success Rate
71.43%
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.
75.00% (15/20)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-11-04 UTC
4 runs
75%Successful runs: 3 of 4 runs (75.0%)
25%E2E failures: 1 of 4 runs (25.0%)
2026-11-05 UTC
6 runs
83%Successful runs: 5 of 6 runs (83.3%)
17%E2E failures: 1 of 6 runs (16.7%)
2026-11-06 UTC
4 runs
75%Successful runs: 3 of 4 runs (75.0%)
25%E2E failures: 1 of 4 runs (25.0%)
2026-11-07 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2026-11-08 UTC
3 runs
67%Successful runs: 2 of 3 runs (66.7%)
33%Other failures: 1 of 3 runs (33.3%)
2026-11-09 UTC
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2026-11-10 UTC
0 runs
No runs

Environment: PROD

E2E Jobs
102
Success Rate
36.27%
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.
37.00% (37/100)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2026-11-04 UTC
24 runs
63%Successful runs: 15 of 24 runs (62.5%)
33%E2E failures: 8 of 24 runs (33.3%)
Other failures: 1 of 24 runs (4.2%)
2026-11-05 UTC
16 runs
63%Successful runs: 10 of 16 runs (62.5%)
31%E2E failures: 5 of 16 runs (31.2%)
Other failures: 1 of 16 runs (6.2%)
2026-11-06 UTC
43 runs
Successful runs: 4 of 43 runs (9.3%)
91%E2E failures: 39 of 43 runs (90.7%)
2026-11-07 UTC
6 runs
100%E2E failures: 6 of 6 runs (100.0%)
2026-11-08 UTC
5 runs
Successful runs: 1 of 5 runs (20.0%)
E2E failures: 4 of 5 runs (80.0%)
2026-11-09 UTC
8 runs
88%Successful runs: 7 of 8 runs (87.5%)
E2E failures: 1 of 8 runs (12.5%)
2026-11-10 UTC
0 runs
No runs