chore(playwright): refresh timing-baseline.json from run 30802611748

[chirag-madlani]

Why

timing-baseline.json on main was captured on 2026-07-22 (sha ccc86fe243) — 12 days ago. Since then 51 commits have touched spec files. The planner's data on origin/main today has drifted heavily:

Signal	Count
Current spec files with zero baseline coverage	30
Baseline titles referencing tests that no longer exist	1007 / 4384 (23%)
Files with title drift (leaf renames, @tag adds, describe restructures)	66 / 322 (20%)
Worst-case dead-baseline: ExplorePageRightPanel	218 / 234 orphans (93%)
Worst-case dead-baseline: AdvancedSearch	107 / 131 orphans (82%)
Worst-case dead-baseline: Lineage/DataAssetLineage	79 / 85 orphans (93%)

That much stale data means LPT is planning against ghosts — the fallback path (30 s per unknown test) is picking up hundreds of tests, and the atomic-unit gate is firing on aggregates that the planner didn't correctly weight.

What

Refresh from the most recent successful full-mode merge_group run (30802611748, 2026-08-03 09:43 UTC, sha 79df9aed95). Its playwright-timing-history-full artifact is retained until 2026-09-02, so this is a clean, verifiable source.

Metadata delta

• 4384 → 4409 tests (25 net additions)
• 322 → 325 files (4 newly covered: Features/ColumnBulkOperationsTagsGlossary, Features/IncidentManagerPagination, Pages/AssetHealthWidget, Pages/PipelineValidation)
• 49 → 14 zero-duration entries (35 previously-skipped tests now have real durations)
• BulkImport correctly recorded under the ImportExport project — PR fix(playwright): route BulkImport back to import-export lane and audit-split the atomic describe #30834's route fix is reflected in the fresh capture (Database service 449 s, Database Schema 366 s, etc.)

Preserved from the current baseline

• retainedUnstableTestIds (68-entry curated allowlist for known flaky tests)
• retainedSourceRunId / retainedSourceSha retention pointers

Schema normalization

Fresh reporter output uses title = › <project> › <file> › <describe> › <leaf> and leafTitle = the short name. Current baseline uses title = short name. Normalized entries to the current baseline's schema (short title, dropped retryDurationMs) so the diff stays a one-line JSON re-serialization.

Test change

Removed a stale assertion in test_versioned_baseline_omits_all_zero_ids_from_weights that required at least one zero-duration entry with outcome=expected. The fresh capture contains only legitimately-skipped zero-ms entries (all outcome=skipped), which is the healthy state. The meaningful part of the test (load-time filtering behavior) still asserts.

Verified

• 64 planner tests pass.
• Simulated load_history against the refreshed baseline: 4395 test_weights entries + 3498 identity_weights (up from partial coverage today).
• BulkImport project correctly on ImportExport with 6 tests × real weights totaling 25.3 min — AUDITED_PARALLEL_SUITES splits into per-spec parallel units so no unit exceeds the 20-min atomic ceiling.

Follow-up (separate PR)

The next PR I'll draft is the workflow step that opens this same refresh PR automatically after every successful full-mode merge_group run — so this doesn't need to be done by hand again.

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

[Copilot]

Pull request overview

Refreshes the checked-in Playwright timing baseline used by the CI shard planner, so planning/weighting reflects the current spec/test structure and avoids fallback-time inflation due to baseline drift.

Changes:

• Updated .github/playwright/timing-baseline.json from a recent successful full-mode run to realign test IDs/titles/durations with origin/main.
• Adjusted test_versioned_baseline_omits_all_zero_ids_from_weights to remove a stale assertion about zero-duration entries having outcome=expected.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/playwright/timing-baseline.json	Refreshes the timing history baseline consumed by the Playwright CI planner.
.github/scripts/tests/test_playwright_ci_planning.py	Updates planner test expectations to match the refreshed baseline’s zero-duration entry shape.

[Copilot]

Pull request overview

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

Suppressed comments (1)

.github/scripts/tests/test_playwright_ci_planning.py:379

• The new assert zero_tests makes this unit test dependent on the checked-in baseline always containing at least one 0-ms entry. A future baseline refresh that happens to have no skipped tests would fail CI even though load_history would still behave correctly. Consider skipping (or switching to a synthetic fixture) when the baseline has no zero-duration entries to avoid false-negative failures during baseline refreshes.

    # Ensure there's something to check — if a future baseline refresh
    # produces a run with zero skipped/0-ms entries, the `all(...)` below
    # would pass vacuously without exercising the filter. Fail loudly
    # instead so whoever refreshed the baseline knows to either construct
    # a synthetic fixture or convert this to a synthetic test.
    assert zero_tests, (
        "checked-in baseline has no zero-duration entries; this test can "
        "no longer exercise the load_history filter path against real data"
    )

[github-actions]

✅ Playwright Results — workflow succeeded

Validated commit 53cea00bce573bfb3487743fe6b8fffd934644b5 in Playwright run 30809113084, attempt 1.

✅ 550 passed · ❌ 0 failed · 🟡 0 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) 51m 15s

⏱️ Max setup 2m 50s · max shard execution 17m 26s · max shard-job elapsed before upload 20m 24s · reporting 4s

🌐 201.36 requests/attempt · 2.83 app boots/UI scenario · 6.02% common-shard skew

Optimization targets still in progress:

• Browser traffic was 201.36 requests per attempt (convergence target: fewer than 200).
• Application boot ratio was 2.83 per UI scenario (1618 boots / 571 scenarios; convergence target: at most 1).

Shard	Passed	Failed	Flaky	Skipped	Lifecycle failed	Lifecycle flaky
✅ Shard chromium-01	143	0	0	3	0	0
✅ Shard chromium-02	134	0	0	0	0	0
✅ Shard chromium-03	122	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 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

[gitar-bot]

Code Review ✅ Approved 1 resolved / 1 findings

Refreshes the Playwright timing baseline and updates test assertions, addressing the vacuous pass finding. No issues found.

✅ 1 resolved

✅ Quality: Test can pass vacuously if no zero-duration entries exist

📄 .github/scripts/tests/test_playwright_ci_planning.py:369-373
After removing the any(...) assertion, test_versioned_baseline_omits_all_zero_ids_from_weights relies solely on assert all(test['id'] not in weights for test in zero_tests), which is vacuously true when zero_tests is empty. A future baseline refresh with zero zero-duration entries would silently make this test meaningless. Consider adding assert zero_tests, ... to guarantee the filtering behavior is actually exercised.

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}