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 batches20834.62% (off track)-60.38pp+5.36pp90.59% (183/202)-4.22pp39.34% (72/183)+5.75pp
INT95% - All E2E job runs0n/a (insufficient data)n/an/an/an/an/an/a
STG95% - All E2E job runs1216.67% (off track)-78.33pp-1.85ppn/an/a16.67% (2/12)-7.14pp
PROD95% - All E2E job runs3743.24% (off track)-51.76pp+15.47ppn/an/a45.71% (16/35)+14.46pp

Environment: DEV

E2E Jobs
491
Success Rate
25.87%
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.
89.29% (417/467)
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.
30.46% (127/417)
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.
208
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.
34.62%
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.
90.59% (183/202)
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.
39.34% (72/183)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
69 runs
23%Successful runs: 16 of 69 runs (23.2%)
Provision failures: 4 of 69 runs (5.8%)
70%E2E failures: 48 of 69 runs (69.6%)
Other failures: 1 of 69 runs (1.4%)
81 runs
30%Successful runs: 24 of 81 runs (29.6%)
Provision failures: 3 of 81 runs (3.7%)
58%E2E failures: 47 of 81 runs (58.0%)
Other failures: 7 of 81 runs (8.6%)
119 runs
20%Successful runs: 24 of 119 runs (20.2%)
Provision failures: 7 of 119 runs (5.9%)
68%E2E failures: 81 of 119 runs (68.1%)
Other failures: 7 of 119 runs (5.9%)
134 runs
24%Successful runs: 32 of 134 runs (23.9%)
12%Provision failures: 16 of 134 runs (11.9%)
57%E2E failures: 77 of 134 runs (57.5%)
Other failures: 9 of 134 runs (6.7%)
75 runs
36%Successful runs: 27 of 75 runs (36.0%)
21%Provision failures: 16 of 75 runs (21.3%)
43%E2E failures: 32 of 75 runs (42.7%)
2 runs
E2E failures: 2 of 2 runs (100.0%)
11 runs
Successful runs: 4 of 11 runs (36.4%)
Provision failures: 4 of 11 runs (36.4%)
E2E failures: 3 of 11 runs (27.3%)

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

Successful runs (post-good + batches) Provision failures E2E failures Other failures
21 runs
38%Successful runs (post-good + batches): 8 of 21 runs (38.1%)
Provision failures: 2 of 21 runs (9.5%)
52%E2E failures: 11 of 21 runs (52.4%)
33 runs
33%Successful runs (post-good + batches): 11 of 33 runs (33.3%)
64%E2E failures: 21 of 33 runs (63.6%)
Other failures: 1 of 33 runs (3.0%)
49 runs
24%Successful runs (post-good + batches): 12 of 49 runs (24.5%)
Provision failures: 2 of 49 runs (4.1%)
69%E2E failures: 34 of 49 runs (69.4%)
Other failures: 1 of 49 runs (2.0%)
71 runs
31%Successful runs (post-good + batches): 22 of 71 runs (31.0%)
15%Provision failures: 11 of 71 runs (15.5%)
48%E2E failures: 34 of 71 runs (47.9%)
Other failures: 4 of 71 runs (5.6%)
25 runs
60%Successful runs (post-good + batches): 15 of 25 runs (60.0%)
Provision failures: 3 of 25 runs (12.0%)
E2E failures: 7 of 25 runs (28.0%)
1 run
E2E failures: 1 of 1 runs (100.0%)
8 runs
Successful runs (post-good + batches): 4 of 8 runs (50.0%)
Provision failures: 1 of 8 runs (12.5%)
E2E failures: 3 of 8 runs (37.5%)

Environment: INT

E2E Jobs
0
Success Rate
0.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.
n/a

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
0 runs
No runs
0 runs
No runs
0 runs
No runs
0 runs
No runs
0 runs
No runs
0 runs
No runs
0 runs
No runs

Environment: STG

E2E Jobs
12
Success Rate
16.67%
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.
16.67% (2/12)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
1 run
100%E2E failures: 1 of 1 runs (100.0%)
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
1 run
100%E2E failures: 1 of 1 runs (100.0%)

Environment: PROD

E2E Jobs
37
Success Rate
43.24%
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.
45.71% (16/35)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
17 runs
59%Successful runs: 10 of 17 runs (58.8%)
29%E2E failures: 5 of 17 runs (29.4%)
12%Other failures: 2 of 17 runs (11.8%)
1 run
E2E failures: 1 of 1 runs (100.0%)
3 runs
100%E2E failures: 3 of 3 runs (100.0%)
11 runs
55%Successful runs: 6 of 11 runs (54.5%)
45%E2E failures: 5 of 11 runs (45.5%)
1 run
E2E failures: 1 of 1 runs (100.0%)
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
2 runs
100%E2E failures: 2 of 2 runs (100.0%)