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 batches7968.35% (off track)-26.65pp+10.29pp93.67% (74/79)+10.88pp72.97% (54/74)+1.69pp
INT95% - All E2E job runs2458.33% (off track)-36.67pp-20.98ppn/an/a82.35% (14/17)-17.65pp
STG95% - All E2E job runs966.67% (off track)-28.33pp-15.48ppn/an/a66.67% (6/9)-18.52pp
PROD95% - All E2E job runs4271.43% (off track)-23.57pp+29.92ppn/an/a71.43% (30/42)+29.52pp

Environment: DEV

E2E Jobs
188
Success Rate
63.30%
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.78% (167/186)
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.26% (119/167)
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.
79
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.35%
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.
93.67% (74/79)
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.
72.97% (54/74)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
57 runs
65%Successful runs: 37 of 57 runs (64.9%)
Provision failures: 5 of 57 runs (8.8%)
25%E2E failures: 14 of 57 runs (24.6%)
Other failures: 1 of 57 runs (1.8%)
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%)
31 runs
68%Successful runs: 21 of 31 runs (67.7%)
Provision failures: 3 of 31 runs (9.7%)
23%E2E failures: 7 of 31 runs (22.6%)
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
24 runs
63%Successful runs (post-good + batches): 15 of 24 runs (62.5%)
Provision failures: 2 of 24 runs (8.3%)
29%E2E failures: 7 of 24 runs (29.2%)
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%)
11 runs
91%Successful runs (post-good + batches): 10 of 11 runs (90.9%)
E2E failures: 1 of 11 runs (9.1%)
0 runs
No runs

Environment: INT

E2E Jobs
24
Success Rate
58.33%
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
7 runs
57%Successful runs: 4 of 7 runs (57.1%)
43%Other failures: 3 of 7 runs (42.9%)
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%)
0 runs
No runs

Environment: STG

E2E Jobs
9
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.
66.67% (6/9)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
3 runs
100%Successful runs: 3 of 3 runs (100.0%)
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%)
0 runs
No runs

Environment: PROD

E2E Jobs
42
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.
71.43% (30/42)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
22 runs
82%Successful runs: 18 of 22 runs (81.8%)
18%E2E failures: 4 of 22 runs (18.2%)
3 runs
Successful runs: 1 of 3 runs (33.3%)
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%)
13 runs
69%Successful runs: 9 of 13 runs (69.2%)
31%E2E failures: 4 of 13 runs (30.8%)
0 runs
No runs