Skip to content

fix: exclude broken regions from E2E tests (Gen 1)#3471

Draft
sarayev wants to merge 2 commits into
release-api-plugin-stablefrom
fix/exclude-regions-gen1
Draft

fix: exclude broken regions from E2E tests (Gen 1)#3471
sarayev wants to merge 2 commits into
release-api-plugin-stablefrom
fix/exclude-regions-gen1

Conversation

@sarayev
Copy link
Copy Markdown
Contributor

@sarayev sarayev commented Apr 14, 2026

Excludes me-south-1 (BAH) and sa-east-1 from E2E test region assignments on the release branch.

These regions have infrastructure issues causing consistent failures:

  • me-south-1 (BAH) — broken RDS infrastructure
  • sa-east-1 — consistent test failures

Note: me-central-1 (DXB) was not present in the release branch region pool, so no change needed.

Changes

  • Removed me-south-1 and sa-east-1 from scripts/e2e-test-regions.json
  • Regenerated codebuild_specs/e2e_workflow.yml (tests redistributed to remaining regions via round-robin)

Testing

  • E2E tests to be triggered and compared against baseline batch ff2330a8-186c-4dca-a677-424287ffe523

These regions have infrastructure issues causing consistent E2E
test failures. Excluding them from the test region pool to reduce
noise and improve signal-to-noise ratio in E2E results.

Regions excluded:
- me-south-1 (BAH) - broken RDS infrastructure
- sa-east-1 - consistent test failures

Note: me-central-1 (DXB) was not present in the release branch
region pool so no change needed for it.
@sarayev sarayev force-pushed the fix/exclude-regions-gen1 branch from 4974dca to e0ea638 Compare April 14, 2026 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant