feat(test-runner): support locks in test.describe.configure - #42792
Devin Rousso (dcrousso) wants to merge 1 commit into
Conversation
locks cannot be declared imperatively for the enclosing suite add a `lock` option to `test.describe.configure` that accumulates suite locks
Test results for "tests 1"8 flaky52059 passed, 1250 skipped Merge workflow run. |
Test results for "MCP"2 failed 8690 passed, 1474 skipped Merge workflow run. |
🟢 Both failures are pre-existing WebMCP flakes — the PR is clearHi, I'm the Playwright bot and I took a look at the red CI here. The two failing MCP tests both fail on unrelated PRs and on DetailsThe "tests 1" report has no failures (8 flaky, all screencast/video/cookie regulars), so there's nothing to triage there. Only the "MCP" report is red, with two failures — both in Pre-existing flake / infra
Both signatures are the same underlying race: the second frame's tool registration hasn't landed by the time Caused by this PR Nothing. The diff is Triaged by the Playwright bot - agent run |
locks cannot be declared imperatively for the enclosing suite
add a
lockoption totest.describe.configurethat accumulates suite locksfixes #42782