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 batches8263.41% (off track)-31.59pp+19.71pp82.93% (68/82)-5.64pp76.47% (52/68)+23.24pp
INT95% - All E2E job runs2272.73% (off track)-22.27pp-0.61ppn/an/a100.00% (16/16)+2.94pp
STG95% - All E2E job runs2185.71% (off track)-9.29pp+34.20ppn/an/a90.00% (18/20)+16.09pp
PROD95% - All E2E job runs6771.64% (off track)-23.36pp+36.16ppn/an/a71.64% (48/67)+34.56pp

Environment: DEV

E2E Jobs
208
Success Rate
57.21%
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.
84.92% (169/199)
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.
70.41% (119/169)
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.
82
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.
63.41%
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.
82.93% (68/82)
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.
76.47% (52/68)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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
54 runs
57%Successful runs: 31 of 54 runs (57.4%)
20%Provision failures: 11 of 54 runs (20.4%)
22%E2E failures: 12 of 54 runs (22.2%)
2026-11-10 UTC
45 runs
60%Successful runs: 27 of 45 runs (60.0%)
16%Provision failures: 7 of 45 runs (15.6%)
22%E2E failures: 10 of 45 runs (22.2%)
Other failures: 1 of 45 runs (2.2%)
2026-11-11 UTC
41 runs
59%Successful runs: 24 of 41 runs (58.5%)
15%Provision failures: 6 of 41 runs (14.6%)
15%E2E failures: 6 of 41 runs (14.6%)
Other failures: 5 of 41 runs (12.2%)
2026-11-12 UTC
50 runs
64%Successful runs: 32 of 50 runs (64.0%)
Provision failures: 3 of 50 runs (6.0%)
26%E2E failures: 13 of 50 runs (26.0%)
Other failures: 2 of 50 runs (4.0%)
2026-11-13 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-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
30 runs
57%Successful runs (post-good + batches): 17 of 30 runs (56.7%)
17%Provision failures: 5 of 30 runs (16.7%)
27%E2E failures: 8 of 30 runs (26.7%)
2026-11-10 UTC
19 runs
58%Successful runs (post-good + batches): 11 of 19 runs (57.9%)
21%Provision failures: 4 of 19 runs (21.1%)
21%E2E failures: 4 of 19 runs (21.1%)
2026-11-11 UTC
17 runs
76%Successful runs (post-good + batches): 13 of 17 runs (76.5%)
Provision failures: 3 of 17 runs (17.6%)
E2E failures: 1 of 17 runs (5.9%)
2026-11-12 UTC
10 runs
70%Successful runs (post-good + batches): 7 of 10 runs (70.0%)
Provision failures: 2 of 10 runs (20.0%)
E2E failures: 1 of 10 runs (10.0%)
2026-11-13 UTC
0 runs
No runs

Environment: INT

E2E Jobs
22
Success Rate
72.73%
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% (16/16)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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
6 runs
100%Successful runs: 6 of 6 runs (100.0%)
2026-11-11 UTC
6 runs
83%Successful runs: 5 of 6 runs (83.3%)
17%Other failures: 1 of 6 runs (16.7%)
2026-11-12 UTC
7 runs
57%Successful runs: 4 of 7 runs (57.1%)
43%Other failures: 3 of 7 runs (42.9%)
2026-11-13 UTC
0 runs
No runs

Environment: STG

E2E Jobs
21
Success Rate
85.71%
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.
90.00% (18/20)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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
5 runs
100%Successful runs: 5 of 5 runs (100.0%)
2026-11-11 UTC
6 runs
100%Successful runs: 6 of 6 runs (100.0%)
2026-11-12 UTC
3 runs
100%Successful runs: 3 of 3 runs (100.0%)
2026-11-13 UTC
0 runs
No runs

Environment: PROD

E2E Jobs
67
Success Rate
71.64%
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.
71.64% (48/67)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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%)
80%E2E failures: 4 of 5 runs (80.0%)
2026-11-09 UTC
9 runs
89%Successful runs: 8 of 9 runs (88.9%)
E2E failures: 1 of 9 runs (11.1%)
2026-11-10 UTC
13 runs
77%Successful runs: 10 of 13 runs (76.9%)
23%E2E failures: 3 of 13 runs (23.1%)
2026-11-11 UTC
14 runs
79%Successful runs: 11 of 14 runs (78.6%)
21%E2E failures: 3 of 14 runs (21.4%)
2026-11-12 UTC
20 runs
90%Successful runs: 18 of 20 runs (90.0%)
E2E failures: 2 of 20 runs (10.0%)
2026-11-13 UTC
0 runs
No runs