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 batches19762.44% (off track)-32.56pp+4.62pp68.23% (131/192)-7.30pp93.89% (123/131)+15.72pp
INT95% - All E2E job runs3145.16% (off track)-49.84pp-13.66ppn/an/a45.16% (14/31)-13.66pp
STG95% - All E2E job runs1643.75% (off track)-51.25pp-56.25ppn/an/a43.75% (7/16)-56.25pp
PROD95% - All E2E job runs2445.83% (off track)-49.17pp+12.50ppn/an/a45.83% (11/24)+12.50pp

Environment: DEV

E2E Jobs
349
Success Rate
51.00%
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.
64.11% (209/326)
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.
85.17% (178/209)
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.
197
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.
62.44%
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.
68.23% (131/192)
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.
93.89% (123/131)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
64 runs
28%Successful runs: 18 of 64 runs (28.1%)
61%Provision failures: 39 of 64 runs (60.9%)
E2E failures: 6 of 64 runs (9.4%)
Other failures: 1 of 64 runs (1.6%)
68 runs
38%Successful runs: 26 of 68 runs (38.2%)
34%Provision failures: 23 of 68 runs (33.8%)
E2E failures: 7 of 68 runs (10.3%)
18%Other failures: 12 of 68 runs (17.6%)
86 runs
44%Successful runs: 38 of 86 runs (44.2%)
45%Provision failures: 39 of 86 runs (45.3%)
E2E failures: 6 of 86 runs (7.0%)
Other failures: 3 of 86 runs (3.5%)
60 runs
65%Successful runs: 39 of 60 runs (65.0%)
27%Provision failures: 16 of 60 runs (26.7%)
E2E failures: 3 of 60 runs (5.0%)
Other failures: 2 of 60 runs (3.3%)
56 runs
77%Successful runs: 43 of 56 runs (76.8%)
16%E2E failures: 9 of 56 runs (16.1%)
Other failures: 4 of 56 runs (7.1%)
15 runs
93%Successful runs: 14 of 15 runs (93.3%)
Other failures: 1 of 15 runs (6.7%)
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
35 runs
40%Successful runs (post-good + batches): 14 of 35 runs (40.0%)
57%Provision failures: 20 of 35 runs (57.1%)
E2E failures: 1 of 35 runs (2.9%)
35 runs
46%Successful runs (post-good + batches): 16 of 35 runs (45.7%)
40%Provision failures: 14 of 35 runs (40.0%)
E2E failures: 1 of 35 runs (2.9%)
Other failures: 4 of 35 runs (11.4%)
47 runs
60%Successful runs (post-good + batches): 28 of 47 runs (59.6%)
36%Provision failures: 17 of 47 runs (36.2%)
E2E failures: 2 of 47 runs (4.3%)
37 runs
70%Successful runs (post-good + batches): 26 of 37 runs (70.3%)
27%Provision failures: 10 of 37 runs (27.0%)
E2E failures: 1 of 37 runs (2.7%)
34 runs
88%Successful runs (post-good + batches): 30 of 34 runs (88.2%)
E2E failures: 3 of 34 runs (8.8%)
Other failures: 1 of 34 runs (2.9%)
9 runs
100%Successful runs (post-good + batches): 9 of 9 runs (100.0%)
0 runs
No runs

Environment: INT

E2E Jobs
31
Success Rate
45.16%
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.16% (14/31)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
5 runs
60%Successful runs: 3 of 5 runs (60.0%)
40%E2E failures: 2 of 5 runs (40.0%)
7 runs
43%Successful runs: 3 of 7 runs (42.9%)
57%E2E failures: 4 of 7 runs (57.1%)
1 run
100%E2E failures: 1 of 1 runs (100.0%)
6 runs
50%Successful runs: 3 of 6 runs (50.0%)
50%E2E failures: 3 of 6 runs (50.0%)
6 runs
67%Successful runs: 4 of 6 runs (66.7%)
33%E2E failures: 2 of 6 runs (33.3%)
3 runs
100%E2E failures: 3 of 3 runs (100.0%)

Environment: STG

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

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
1 run
100%E2E failures: 1 of 1 runs (100.0%)
4 runs
50%Successful runs: 2 of 4 runs (50.0%)
50%E2E failures: 2 of 4 runs (50.0%)
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
1 run
100%Successful runs: 1 of 1 runs (100.0%)
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
3 runs
33%Successful runs: 1 of 3 runs (33.3%)
67%E2E failures: 2 of 3 runs (66.7%)
1 run
100%Successful runs: 1 of 1 runs (100.0%)

Environment: PROD

E2E Jobs
24
Success Rate
45.83%
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.83% (11/24)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
1 run
100%E2E failures: 1 of 1 runs (100.0%)
3 runs
100%E2E failures: 3 of 3 runs (100.0%)
3 runs
100%E2E failures: 3 of 3 runs (100.0%)
5 runs
20%Successful runs: 1 of 5 runs (20.0%)
80%E2E failures: 4 of 5 runs (80.0%)
1 run
100%Successful runs: 1 of 1 runs (100.0%)
2 runs
50%Successful runs: 1 of 2 runs (50.0%)
50%E2E failures: 1 of 2 runs (50.0%)
9 runs
89%Successful runs: 8 of 9 runs (88.9%)
11%E2E failures: 1 of 9 runs (11.1%)