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 only runs that happened after the final push to a PR that later merged.
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 only runs after the final push to a PR that later merged. 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% - After last push of a PR that merges15440.26% (off track)-54.74pp-10.01pp90.54% (134/148)-2.24pp46.27% (62/134)-9.42pp
INT95% - All E2E job runs2661.54% (off track)-33.46pp+5.66ppn/an/a66.67% (16/24)+7.29pp
STG95% - All E2E job runs2412.50% (off track)-82.50pp+7.95ppn/an/a13.04% (3/23)+8.28pp
PROD95% - All E2E job runs3432.35% (off track)-62.65pp+11.76ppn/an/a33.33% (11/33)+12.12pp

Environment: DEV

E2E Jobs
626
Success Rate
19.81%
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.
87.29% (460/527)
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.
26.96% (124/460)
E2E Jobs (after last push of merged PR)
These DEV-only metrics include only runs that happened after the final push to a PR that later merged. This gives a view of the signal closest to what actually landed, rather than earlier trial runs from the same PR. This card shows the number of runs in that DEV-only goal basis.
154
Success Rate (after last push of merged PR)
These DEV-only metrics include only runs that happened after the final push to a PR that later merged. This gives a view of the signal closest to what actually landed, rather than earlier trial runs from the same PR. This card shows the overall success rate for that DEV-only goal basis.
40.26%
Provision success (after last push of merged PR)
These DEV-only metrics include only runs that happened after the final push to a PR that later merged. This gives a view of the signal closest to what actually landed, rather than earlier trial runs from the same PR. 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.54% (134/148)
E2E success (after last push of merged PR)
These DEV-only metrics include only runs that happened after the final push to a PR that later merged. This gives a view of the signal closest to what actually landed, rather than earlier trial runs from the same PR. 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.
46.27% (62/134)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
107 runs
32%Successful runs: 34 of 107 runs (31.8%)
Provision failures: 6 of 107 runs (5.6%)
54%E2E failures: 58 of 107 runs (54.2%)
Other failures: 9 of 107 runs (8.4%)
133 runs
29%Successful runs: 38 of 133 runs (28.6%)
Provision failures: 5 of 133 runs (3.8%)
45%E2E failures: 60 of 133 runs (45.1%)
23%Other failures: 30 of 133 runs (22.6%)
127 runs
12%Successful runs: 15 of 127 runs (11.8%)
12%Provision failures: 15 of 127 runs (11.8%)
68%E2E failures: 86 of 127 runs (67.7%)
Other failures: 11 of 127 runs (8.7%)
28 runs
Successful runs: 9 of 28 runs (32.1%)
Provision failures: 1 of 28 runs (3.6%)
54%E2E failures: 15 of 28 runs (53.6%)
Other failures: 3 of 28 runs (10.7%)
3 runs
Successful runs: 2 of 3 runs (66.7%)
E2E failures: 1 of 3 runs (33.3%)
103 runs
Successful runs: 13 of 103 runs (12.6%)
34%Provision failures: 35 of 103 runs (34.0%)
47%E2E failures: 48 of 103 runs (46.6%)
Other failures: 7 of 103 runs (6.8%)
125 runs
Successful runs: 13 of 125 runs (10.4%)
Provision failures: 5 of 125 runs (4.0%)
54%E2E failures: 68 of 125 runs (54.4%)
31%Other failures: 39 of 125 runs (31.2%)

Daily Run Outcomes for DEV Goal Basis (after last push of merged PR)

Successful runs (after last push of merged PR) Provision failures E2E failures Other failures
48 runs
48%Successful runs (after last push of merged PR): 23 of 48 runs (47.9%)
Provision failures: 2 of 48 runs (4.2%)
48%E2E failures: 23 of 48 runs (47.9%)
38 runs
55%Successful runs (after last push of merged PR): 21 of 38 runs (55.3%)
42%E2E failures: 16 of 38 runs (42.1%)
Other failures: 1 of 38 runs (2.6%)
40 runs
25%Successful runs (after last push of merged PR): 10 of 40 runs (25.0%)
13%Provision failures: 5 of 40 runs (12.5%)
60%E2E failures: 24 of 40 runs (60.0%)
Other failures: 1 of 40 runs (2.5%)
10 runs
Successful runs (after last push of merged PR): 3 of 10 runs (30.0%)
Provision failures: 1 of 10 runs (10.0%)
E2E failures: 4 of 10 runs (40.0%)
Other failures: 2 of 10 runs (20.0%)
0 runs
No runs
11 runs
Successful runs (after last push of merged PR): 3 of 11 runs (27.3%)
55%Provision failures: 6 of 11 runs (54.5%)
E2E failures: 2 of 11 runs (18.2%)
7 runs
Successful runs (after last push of merged PR): 2 of 7 runs (28.6%)
E2E failures: 3 of 7 runs (42.9%)
Other failures: 2 of 7 runs (28.6%)

Environment: INT

E2E Jobs
26
Success Rate
61.54%
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% (16/24)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
7 runs
71%Successful runs: 5 of 7 runs (71.4%)
29%E2E failures: 2 of 7 runs (28.6%)
7 runs
71%Successful runs: 5 of 7 runs (71.4%)
14%E2E failures: 1 of 7 runs (14.3%)
14%Other failures: 1 of 7 runs (14.3%)
2 runs
100%E2E failures: 2 of 2 runs (100.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%)
6 runs
67%Successful runs: 4 of 6 runs (66.7%)
33%E2E failures: 2 of 6 runs (33.3%)
1 run
100%Other failures: 1 of 1 runs (100.0%)

Environment: STG

E2E Jobs
24
Success Rate
12.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.
13.04% (3/23)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
6 runs
100%E2E failures: 6 of 6 runs (100.0%)
6 runs
100%E2E failures: 6 of 6 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%)
2 runs
100%E2E failures: 2 of 2 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
67%Successful runs: 2 of 3 runs (66.7%)
33%Other failures: 1 of 3 runs (33.3%)

Environment: PROD

E2E Jobs
34
Success Rate
32.35%
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.
33.33% (11/33)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
12 runs
25%Successful runs: 3 of 12 runs (25.0%)
75%E2E failures: 9 of 12 runs (75.0%)
6 runs
67%Successful runs: 4 of 6 runs (66.7%)
33%E2E failures: 2 of 6 runs (33.3%)
2 runs
100%E2E failures: 2 of 2 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%)
2 runs
100%E2E failures: 2 of 2 runs (100.0%)
8 runs
50%Successful runs: 4 of 8 runs (50.0%)
38%E2E failures: 3 of 8 runs (37.5%)
Other failures: 1 of 8 runs (12.5%)