chore(ui): move autopilot to first runner

[karanh37]

chore(ui): move autopilot to first runner

---

Summary by Gitar

• New isolated test runner:
  • Created dedicated IsolatedTests Playwright project for AutoPilot E2E tests in playwright.config.ts
• CI pipeline configuration:
  • Added IsolatedTests project to shard 1 in all CI workflows (MySQL/PostgreSQL nightly and E2E)
• Test isolation improvement:
  • AutoPilot tests now run separately with only setup dependency, excluded from main chromium runner

_{This will update automatically on new commits.}

---

[github-actions]

Jest test Coverage

UI tests summary

Lines	Statements	Branches	Functions
	65.77% (55191/83909)	44.77% (28466/63584)	47.73% (8679/18185)

[gitar-bot]

🔍 CI failure analysis for c2fd3e6: CRITICAL: Retry also failed. Shard 1/5 now has 75% failure rate (3 of 4 attempts). Infrastructure issue persists with 215 failures. This is a systemic CI problem requiring immediate infrastructure fixes, NOT a PR code issue.

CRITICAL: Infrastructure Failure Persists Despite Retry

Shard 1/5 Complete History

Attempt	Result	Failures	Status
1	❌	249	Backend unresponsive
2	✅	3	SUCCESS (genuine failures only)
3	❌	206	Infrastructure (3.6h duration)
4 (Retry)	❌	215	Infrastructure persists (3.6h)

Success Rate: 25% (1 of 4 attempts)

Infrastructure Failure Rate: 75%

---

Attempt 4 Analysis (Latest Retry)

Status: 215 tests failed, 322 passed, 2 flaky

Duration: 3.6 hours

Critical Finding: Retry did NOT resolve the issue - failures actually increased slightly (206 → 215)

Error Escalation:

• page.goto timeouts: 14 → 31 (doubled)
• Same pattern: backend degradation over 3.6-hour run
• Same error types: timeouts, elements not found, cleanup failures

---

Root Cause: Confirmed Systemic Issue

Three consecutive infrastructure failures with the same pattern prove this is NOT a random flake:

1. Duration correlation: All 3 failures after 3.6-4 hours
2. Progressive degradation: Service works initially, degrades over time
3. Similar failure counts: 249 → 206 → 215
4. Persistent across retries: Retry didn't help

Diagnosis: CI infrastructure cannot sustain 3.6-hour test runs for this shard

Likely causes:

• Memory leaks accumulating over hours
• Database connection pool exhaustion
• Resource limits insufficient
• No health checks or periodic restarts

---

Known Genuine Failures

From successful Attempt 2: Only 3 genuine test failures

• All in ColumnBulkOperations (loader issue)
• Pre-existing bugs

The 200+ failures in Attempts 1, 3, 4 are ALL infrastructure-related.

---

Relationship to PR

NOT caused by this PR. This PR only changes:

• AutoPilot test configuration (separate project)
• CI workflow organization
• No backend/infrastructure code

This is a critical CI environment reliability issue.

---

Other Shard Status

Shard 3/5: Also had issues but improved 18→3 on retry. Currently has 3 genuine pre-existing failures.

Code Review ✅ Approved

Clean CI configuration change to isolate AutoPilot E2E tests. The changes are consistent across all workflow files and the Playwright config properly excludes the tests from the main runner while creating a dedicated isolated project.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqubecloud]

Quality Gate passed for 'open-metadata-ui'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud