updated playwright trace config to retain trace on failure to get trace for flaky test

[ShaileshParmar11]

Describe your changes:

Fixes #

I worked on ... because ...

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

High-level design:

N/A — small change.

Tests:

Use cases covered

Unit tests

Backend integration tests

Ingestion integration tests

Playwright (UI) tests

Manual testing performed

UI screen recording / screenshots:

Not applicable.

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• My PR is linked to a GitHub issue via Fixes #<issue-number> above.
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.
• For UI changes: I attached a screen recording and/or screenshots above.
• I have added tests (unit / integration / Playwright as applicable) and listed them above.

[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.

[github-actions]

🔴 Playwright Results — workflow failed

Validated commit aab79469eb10fa690fa361bd846fff71db098b2c in Playwright run 31157606268, attempt 1.

✅ 271 passed · ❌ 0 failed · 🟡 0 flaky · ⏭️ 0 skipped · 🧰 0 lifecycle flaky

Pipeline and setup failures (5)

• Playwright coverage validation found 279 missing, 0 unexpected, 0 duplicate-plan, and 0 duplicate-execution test ID(s).
• Shard chromium-02 did not upload a usable Playwright results artifact.
• Shard chromium-03 did not upload a usable Playwright results artifact.
• Shard chromium-02 test execution finished with status failure without a reported test failure.
• Shard chromium-03 test execution finished with status failure without a reported test failure.

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) 1h 1m 47s

⏱️ Max setup 3m 35s · max shard execution 25m 0s · max shard-job elapsed before upload 28m 37s · reporting 3s

🌐 392.49 requests/attempt · 2.90 app boots/UI scenario · 19.20% common-shard skew

Optimization targets still in progress:

• Common shard skew was 19.2% (convergence target: at most 15%).
• Browser traffic was 392.49 requests per attempt (convergence target: fewer than 200).
• Application boot ratio was 2.9 per UI scenario (1559 boots / 537 scenarios; convergence target: at most 1).

Shard	Passed	Failed	Flaky	Skipped	Lifecycle failed	Lifecycle flaky
✅ Shard chromium-01	120	0	0	0	0	0
⛔ Shard chromium-02	—	—	—	—	—	—
⛔ Shard chromium-03	—	—	—	—	—	—
✅ 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 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

📦 Download artifacts

How to debug locally

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

[ShaileshParmar11]

Closing it, its increasing load at run side, need better handling for it before enabling it

[gitar-bot]

Code Review ✅ Approved

Updates Playwright trace configuration to retain traces on failure for improved flaky test debugging. 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 👍 / 👎 | Powered by Gitar — free for open source}