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 batches14729.25% (off track)-65.75pp-6.56pp94.81% (128/135)+0.76pp33.59% (43/128)-6.93pp
INT95% - All E2E job runs2352.17% (off track)-42.83pp-1.16ppn/an/a52.17% (12/23)-4.97pp
STG95% - All E2E job runs2718.52% (off track)-76.48pp+8.17ppn/an/a23.81% (5/21)+12.27pp
PROD95% - All E2E job runs3627.78% (off track)-67.22pp-9.06ppn/an/a31.25% (10/32)-5.59pp

Environment: DEV

E2E Jobs
407
Success Rate
19.90%
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.
91.78% (346/377)
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.
23.41% (81/346)
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.
147
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.
29.25%
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.81% (128/135)
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.
33.59% (43/128)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
77 runs
13%Successful runs: 10 of 77 runs (13.0%)
Provision failures: 6 of 77 runs (7.8%)
73%E2E failures: 56 of 77 runs (72.7%)
Other failures: 5 of 77 runs (6.5%)
85 runs
14%Successful runs: 12 of 85 runs (14.1%)
Provision failures: 8 of 85 runs (9.4%)
67%E2E failures: 57 of 85 runs (67.1%)
Other failures: 8 of 85 runs (9.4%)
71 runs
14%Successful runs: 10 of 71 runs (14.1%)
Provision failures: 5 of 71 runs (7.0%)
70%E2E failures: 50 of 71 runs (70.4%)
Other failures: 6 of 71 runs (8.5%)
91 runs
27%Successful runs: 25 of 91 runs (27.5%)
Provision failures: 6 of 91 runs (6.6%)
59%E2E failures: 54 of 91 runs (59.3%)
Other failures: 6 of 91 runs (6.6%)
59 runs
29%Successful runs: 17 of 59 runs (28.8%)
Provision failures: 6 of 59 runs (10.2%)
54%E2E failures: 32 of 59 runs (54.2%)
Other failures: 4 of 59 runs (6.8%)
14 runs
Successful runs: 7 of 14 runs (50.0%)
E2E failures: 7 of 14 runs (50.0%)
10 runs
E2E failures: 9 of 10 runs (90.0%)
Other failures: 1 of 10 runs (10.0%)

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

Successful runs (post-good + batches) Provision failures E2E failures Other failures
19 runs
26%Successful runs (post-good + batches): 5 of 19 runs (26.3%)
63%E2E failures: 12 of 19 runs (63.2%)
Other failures: 2 of 19 runs (10.5%)
21 runs
43%Successful runs (post-good + batches): 9 of 21 runs (42.9%)
48%E2E failures: 10 of 21 runs (47.6%)
Other failures: 2 of 21 runs (9.5%)
23 runs
Successful runs (post-good + batches): 4 of 23 runs (17.4%)
Provision failures: 2 of 23 runs (8.7%)
61%E2E failures: 14 of 23 runs (60.9%)
Other failures: 3 of 23 runs (13.0%)
44 runs
30%Successful runs (post-good + batches): 13 of 44 runs (29.5%)
Provision failures: 4 of 44 runs (9.1%)
57%E2E failures: 25 of 44 runs (56.8%)
Other failures: 2 of 44 runs (4.5%)
23 runs
30%Successful runs (post-good + batches): 7 of 23 runs (30.4%)
Provision failures: 1 of 23 runs (4.3%)
57%E2E failures: 13 of 23 runs (56.5%)
Other failures: 2 of 23 runs (8.7%)
11 runs
45%Successful runs (post-good + batches): 5 of 11 runs (45.5%)
55%E2E failures: 6 of 11 runs (54.5%)
6 runs
83%E2E failures: 5 of 6 runs (83.3%)
Other failures: 1 of 6 runs (16.7%)

Environment: INT

E2E Jobs
23
Success Rate
52.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.
52.17% (12/23)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
6 runs
50%Successful runs: 3 of 6 runs (50.0%)
50%E2E failures: 3 of 6 runs (50.0%)
7 runs
29%Successful runs: 2 of 7 runs (28.6%)
71%E2E failures: 5 of 7 runs (71.4%)
4 runs
100%Successful runs: 4 of 4 runs (100.0%)
6 runs
50%Successful runs: 3 of 6 runs (50.0%)
50%E2E failures: 3 of 6 runs (50.0%)
0 runs
No runs
0 runs
No runs
0 runs
No runs

Environment: STG

E2E Jobs
27
Success Rate
18.52%
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.
23.81% (5/21)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
4 runs
75%E2E failures: 3 of 4 runs (75.0%)
25%Other failures: 1 of 4 runs (25.0%)
5 runs
40%E2E failures: 2 of 5 runs (40.0%)
60%Other failures: 3 of 5 runs (60.0%)
6 runs
83%E2E failures: 5 of 6 runs (83.3%)
17%Other failures: 1 of 6 runs (16.7%)
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%)
4 runs
50%Successful runs: 2 of 4 runs (50.0%)
50%E2E failures: 2 of 4 runs (50.0%)
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)

Environment: PROD

E2E Jobs
36
Success Rate
27.78%
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.
31.25% (10/32)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
5 runs
40%Successful runs: 2 of 5 runs (40.0%)
60%E2E failures: 3 of 5 runs (60.0%)
3 runs
100%E2E failures: 3 of 3 runs (100.0%)
7 runs
86%E2E failures: 6 of 7 runs (85.7%)
14%Other failures: 1 of 7 runs (14.3%)
7 runs
14%Successful runs: 1 of 7 runs (14.3%)
71%E2E failures: 5 of 7 runs (71.4%)
14%Other failures: 1 of 7 runs (14.3%)
9 runs
56%Successful runs: 5 of 9 runs (55.6%)
22%E2E failures: 2 of 9 runs (22.2%)
22%Other failures: 2 of 9 runs (22.2%)
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)