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 batches6973.91% (off track)-21.09pp+11.52pp95.65% (66/69)+10.18pp77.27% (51/66)+4.27pp
INT95% - All E2E job runs2458.33% (off track)-36.67pp-14.39ppn/an/a82.35% (14/17)-17.65pp
STG95% - All E2E job runs862.50% (off track)-32.50pp-19.32ppn/an/a62.50% (5/8)-23.21pp
PROD95% - All E2E job runs3464.71% (off track)-30.29pp-3.35ppn/an/a64.71% (22/34)-3.35pp

Environment: DEV

E2E Jobs
173
Success Rate
64.16%
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.
93.60% (161/172)
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.
68.94% (111/161)
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.
69
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.
73.91%
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.
95.65% (66/69)
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.
77.27% (51/66)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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%)
44 runs
55%Successful runs: 24 of 44 runs (54.5%)
Provision failures: 1 of 44 runs (2.3%)
43%E2E failures: 19 of 44 runs (43.2%)
33 runs
70%Successful runs: 23 of 33 runs (69.7%)
Provision failures: 2 of 33 runs (6.1%)
24%E2E failures: 8 of 33 runs (24.2%)
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
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%)
13 runs
62%Successful runs (post-good + batches): 8 of 13 runs (61.5%)
38%E2E failures: 5 of 13 runs (38.5%)
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%)
17 runs
71%Successful runs (post-good + batches): 12 of 17 runs (70.6%)
Provision failures: 1 of 17 runs (5.9%)
24%E2E failures: 4 of 17 runs (23.5%)
8 runs
100%Successful runs (post-good + batches): 8 of 8 runs (100.0%)
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
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%)
3 runs
100%Other failures: 3 of 3 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%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%)
1 run
100%E2E failures: 1 of 1 runs (100.0%)
0 runs
No runs

Environment: PROD

E2E Jobs
34
Success Rate
64.71%
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.
64.71% (22/34)

Daily Run Outcomes

Successful runs Provision failures E2E failures Other failures
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%)
10 runs
70%Successful runs: 7 of 10 runs (70.0%)
30%E2E failures: 3 of 10 runs (30.0%)
5 runs
80%Successful runs: 4 of 5 runs (80.0%)
E2E failures: 1 of 5 runs (20.0%)
0 runs
No runs