fix(playwright): route BulkImport back to import-export lane and audit-split the atomic describe

[chirag-madlani]

Summary

The merge-queue plan step for PR #30697 failed with:

Atomic Playwright units exceed the 20-minute execution budget; refactor or explicitly
audit them for parallel splitting: chromium|Features/BulkImport.spec.ts|Bulk Import Export (25.8m)

Two orthogonal issues from #30458's re-enable of the suite, both fixed here.

Issue 1 — the @import-export tag was dropped along with .fixme

Before #30458:

test.describe.fixme('Bulk Import Export', { tag: '@import-export' }, () => { … })

After #30458 (current origin/main):

test.describe('Bulk Import Export', () => { … })

.fixme was removed correctly, but the { tag: '@import-export' } option went with it. Without the tag:

• ImportExport project's grep: combineGrep(/@import-export/) doesn't match → tests are excluded from the dedicated project.
• chromium project's grepInvert: [.., /@import-export/, ..] (active with PW_DEDICATED_IMPORT_EXPORT=true) doesn't exclude them → they land on the chromium lane.

Fix: restore the tag on the describe. The whole suite routes back to the dedicated ImportExport project → import-export lane.

Issue 2 — the atomic-unit ceiling still trips even in the import-export lane

The Bulk Import Export describe wraps six tests, each declaring test.setTimeout(300_000-600_000) (5-10 min per test). The planner's oversized_units check compares each unit's weight_ms against TARGET_MS = 20 * 60 * 1000 regardless of destination lane — so a >20-min aggregate breaks the plan step wherever it lands.

Fix: add ("Features/BulkImport.spec.ts", "Bulk Import Export") to AUDITED_PARALLEL_SUITES. discover_units then splits the describe into six per-spec parallel units. Module-scoped entity constructors (new UserClass(), new GlossaryClass() etc.) generate unique names per test instance, so each parallel unit brings its own beforeAll state without cross-worker collision.

Verification

• 64 planning tests pass locally.
• Reproduced the split against a synthetic test-list mirroring the CI shape — one atomic unit becomes six per-spec units (each carrying one test id).
• Prettier + ESLint clean on the modified spec.

Test plan

• Next merge-queue run: plan step succeeds, matrix includes an import-export shard with BulkImport specs.
• BulkImport tests execute on the import-export lane (visible in the shard-job name), not chromium.
• Chromium lane content drops by the BulkImport aggregate — small headroom win.

Related: #30812 (planner all-zero-history fix), #30822 (glossary hang fix).

🤖 Generated with Claude Code

[github-actions]

❌ PR checklist incomplete

This PR cannot be merged until the following are addressed on its linked issue:

• No GitHub issue is linked. Link an issue in the Development section of the PR (or add Fixes #12345 to the description). For a same-org cross-repo issue, add Fixes open-metadata/<repo>#123 to the description.

The fields live on the linked issue in the Shipping project (open the issue → right sidebar → Projects). After you set them, re-run this check (or push a commit) — issue/project changes do not re-trigger it automatically.

Maintainers can bypass this check by adding the skip-pr-checks label.

[gitar-bot]

Code Review ✅ Approved

Restores the @import-export tag and adds BulkImport to AUDITED_PARALLEL_SUITES to fix CI execution budget failures and route tests back to the correct lane. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar | Powered by Gitar — free for open source}

[Copilot]

Pull request overview

This PR fixes Playwright CI sharding/planning by ensuring the BulkImport suite is (1) routed to the dedicated Import/Export lane again and (2) split into audited per-spec units so it no longer violates the 20-minute atomic-unit budget enforced by the shard planner.

Changes:

• Restores the @import-export tag on the Bulk Import Export describe, so the suite is picked up by the ImportExport Playwright project and excluded from the chromium lane when PW_DEDICATED_IMPORT_EXPORT=true.
• Adds ("Features/BulkImport.spec.ts", "Bulk Import Export") to AUDITED_PARALLEL_SUITES, enabling the planner to split the suite into per-spec parallel units instead of treating the whole describe as one oversized atomic unit.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
openmetadata-ui/src/main/resources/ui/playwright/e2e/Features/BulkImport.spec.ts	Re-adds the @import-export tag to route the suite back to the ImportExport lane.
.github/scripts/build_playwright_shards.py	Audits/splits Bulk Import Export into per-spec units to satisfy the planner’s atomic-unit runtime ceiling.

[github-actions]

✅ Playwright Results — workflow succeeded

Validated commit 700a18337b57f70418844a5c8357fac9dd0bbeb7 in Playwright run 30785721057, attempt 1.

✅ 554 passed · ❌ 0 failed · 🟡 2 flaky · ⏭️ 3 skipped · 🧰 0 lifecycle flaky

Performance

Blocking targets: ✅ met · Optimization targets: 🟡 in progress

Shard-job maxima below are not the full workflow wall time; the linked run includes build, fixture, planning, and reporting.

🕒 Full workflow signal wall (to summary) 52m 11s

⏱️ Max setup 3m 1s · max shard execution 19m 5s · max shard-job elapsed before upload 22m 0s · reporting 5s

🌐 203.56 requests/attempt · 2.81 app boots/UI scenario · 2.55% common-shard skew

Optimization targets still in progress:

• Browser traffic was 203.56 requests per attempt (convergence target: fewer than 200).
• Application boot ratio was 2.81 per UI scenario (1629 boots / 579 scenarios; convergence target: at most 1).

Shard	Passed	Failed	Flaky	Skipped	Lifecycle failed	Lifecycle flaky
🟡 Shard chromium-01	147	0	1	3	0	0
✅ Shard chromium-02	132	0	0	0	0	0
✅ Shard chromium-03	119	0	0	0	0	0
✅ Shard data-asset-rules-01	61	0	0	0	0	0
✅ Shard domain-isolation-01	14	0	0	0	0	0
✅ Shard global-state-01	34	0	0	0	0	0
🟡 Shard import-export-01	5	0	1	0	0	0
✅ Shard ingestion-01	1	0	0	0	0	0
✅ Shard reindex-01	2	0	0	0	0	0
✅ Shard search-01	10	0	0	0	0	0
✅ Shard search-rbac-01	29	0	0	0	0	0

🟡 2 flaky test(s) (passed on retry)

• Pages/Entity.spec.ts › Domain Propagation (shard chromium-01, 1 retry)
• Features/BulkImport.spec.ts › Range selection (shard import-export-01, 1 retry)

📦 Download artifacts

How to debug locally

# Download playwright-test-results-<shard> artifact and unzip
npx playwright show-trace path/to/trace.zip    # view trace

[github-actions]

🚦 Removed from the merge queue — manual (2026-08-03T09:14:36Z)

Blocked the queue: playwright-summary, integration-tests-mysql-elasticsearch

• Integration Tests - PostgreSQL + Elasticsearch + Redis — integration-tests-postgres-elasticsearch-redis, Detect Changes
• Postgresql PR Playwright E2E Tests — playwright-summary, detect-changes
• Integration Tests - MySQL + Elasticsearch — integration-tests-mysql-elasticsearch, Detect Changes

[github-actions]

🚦 Removed from the merge queue — manual (2026-08-03T10:44:48Z)

Blocked the queue: playwright-summary

• Postgresql PR Playwright E2E Tests — playwright-summary, playwright-ci-postgresql (ingestion-01), playwright-ci-postgresql (chromium-17), playwright-ci-postgresql (chromium-10)