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 batches7268.06% (off track)-26.94pp+9.79pp91.67% (66/72)+8.33pp74.24% (49/66)+3.77pp
INT95% - All E2E job runs2166.67% (off track)-28.33pp-4.76ppn/an/a82.35% (14/17)-17.65pp
STG95% - All E2E job runs862.50% (off track)-32.50pp-21.50ppn/an/a62.50% (5/8)-25.00pp
PROD95% - All E2E job runs2751.85% (off track)-43.15pp+5.42ppn/an/a51.85% (14/27)+5.42pp

Environment: DEV

E2E Jobs
180
Success Rate
61.11%
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.57% (163/178)
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.
67.48% (110/163)
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.
72
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.
68.06%
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.
91.67% (66/72)
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.
74.24% (49/66)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
41 runs
56%Successful runs: 23 of 41 runs (56.1%)
15%Provision failures: 6 of 41 runs (14.6%)
29%E2E failures: 12 of 41 runs (29.3%)
14 runs
57%Successful runs: 8 of 14 runs (57.1%)
Provision failures: 3 of 14 runs (21.4%)
E2E failures: 3 of 14 runs (21.4%)
14 runs
79%Successful runs: 11 of 14 runs (78.6%)
Provision failures: 2 of 14 runs (14.3%)
E2E failures: 1 of 14 runs (7.1%)
31 runs
61%Successful runs: 19 of 31 runs (61.3%)
35%E2E failures: 11 of 31 runs (35.5%)
Other failures: 1 of 31 runs (3.2%)
37 runs
70%Successful runs: 26 of 37 runs (70.3%)
Provision failures: 3 of 37 runs (8.1%)
22%E2E failures: 8 of 37 runs (21.6%)
43 runs
53%Successful runs: 23 of 43 runs (53.5%)
Provision failures: 1 of 43 runs (2.3%)
42%E2E failures: 18 of 43 runs (41.9%)
Other failures: 1 of 43 runs (2.3%)
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
19 runs
58%Successful runs (post-good + batches): 11 of 19 runs (57.9%)
16%Provision failures: 3 of 19 runs (15.8%)
26%E2E failures: 5 of 19 runs (26.3%)
6 runs
83%Successful runs (post-good + batches): 5 of 6 runs (83.3%)
E2E failures: 1 of 6 runs (16.7%)
7 runs
86%Successful runs (post-good + batches): 6 of 7 runs (85.7%)
E2E failures: 1 of 7 runs (14.3%)
12 runs
58%Successful runs (post-good + batches): 7 of 12 runs (58.3%)
42%E2E failures: 5 of 12 runs (41.7%)
18 runs
67%Successful runs (post-good + batches): 12 of 18 runs (66.7%)
11%Provision failures: 2 of 18 runs (11.1%)
22%E2E failures: 4 of 18 runs (22.2%)
10 runs
80%Successful runs (post-good + batches): 8 of 10 runs (80.0%)
Provision failures: 1 of 10 runs (10.0%)
E2E failures: 1 of 10 runs (10.0%)
0 runs
No runs

Environment: INT

E2E Jobs
21
Success Rate
66.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.
82.35% (14/17)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
0 runs
No runs
5 runs
40%Successful runs: 2 of 5 runs (40.0%)
60%E2E failures: 3 of 5 runs (60.0%)
3 runs
100%Successful runs: 3 of 3 runs (100.0%)
5 runs
60%Successful runs: 3 of 5 runs (60.0%)
40%Other failures: 2 of 5 runs (40.0%)
4 runs
50%Successful runs: 2 of 4 runs (50.0%)
50%Other failures: 2 of 4 runs (50.0%)
4 runs
100%Successful runs: 4 of 4 runs (100.0%)
0 runs
No runs

Environment: STG

E2E Jobs
8
Success Rate
62.50%
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.
62.50% (5/8)

Daily Run Outcomes

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

Environment: PROD

E2E Jobs
27
Success Rate
51.85%
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.
51.85% (14/27)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
3 runs
Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
1 run
Successful runs: 1 of 1 runs (100.0%)
2 runs
Successful runs: 1 of 2 runs (50.0%)
E2E failures: 1 of 2 runs (50.0%)
1 run
E2E failures: 1 of 1 runs (100.0%)
15 runs
60%Successful runs: 9 of 15 runs (60.0%)
40%E2E failures: 6 of 15 runs (40.0%)
5 runs
40%Successful runs: 2 of 5 runs (40.0%)
60%E2E failures: 3 of 5 runs (60.0%)
0 runs
No runs