Skip to content

test: avoid large core dumps in crash tests - #44102

Open
microsoft-playwright-automation[bot] wants to merge 1 commit into
mainfrom
triage/44094/43456019475-1
Open

microsoft-playwright-automation[bot] wants to merge 1 commit into
mainfrom
triage/44094/43456019475-1

Conversation

@microsoft-playwright-automation

Copy link
Copy Markdown
Contributor

Linux core handlers can spend longer than the test timeout dumping a renderer's address space, delaying its crash event. Piped handlers ignore RLIMIT_CORE=0.

Set coredump_filter=0 in intentional-crash test workers before they launch browsers. Keep Chrome's sandbox enabled, leave other workers and host settings unchanged, and remove the Ubuntu-specific skips.

Verified the regression fails without the fixture and passes with it. Headless MCP crash/CDP tests: 44 passed, 20 skipped. Library crash/page-close tests: 26 passed per browser in Chromium, Firefox and WebKit. Build and flint pass. Separate headed MCP recovery failures also reproduce without the fixture and with the sandbox disabled.

Fixes #44094

Triaged on Linux by the Playwright bot - agent run

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "MCP"

1 failed
❌ [webkit] › mcp/http.spec.ts:92 › http transport browser lifecycle (isolated) @mcp-ubuntu-latest-webkit

5234 passed, 631 skipped


Merge workflow run.

@microsoft-playwright-automation

Copy link
Copy Markdown
Contributor Author

🟢 The only failure is a confirmed pre-existing flake

Hi, I'm the Playwright bot. I checked the MCP failure; the evidence does not point to this PR.

Details

Covers MCP run 43459336336, attempt 1, for head a7ca6a23175bb718ec31771dd87e23b93412a670. The merged report has one failure.

Pre-existing flake / infra

The PR enables crashTestFixtures only in the two crash-test files. The HTTP test imports the unchanged MCP fixtures and does not enable the new core-dump filter. No failure is attributed to the PR.

Checked the failures on Linux - agent run

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "tests 1"

4 flaky ⚠️ [installation tests] › connect-to-selenium.spec.ts:20 › connect to selenium `@package-installations-ubuntu-latest`
⚠️ [chromium-library] › library/chromium/connect-to-worker.spec.ts:19 › CR-043 should connect, evaluate, receive console and disconnect `@chromium-playwright-x64-ubuntu24-64-core-node22`
⚠️ [chromium-library] › library/video.spec.ts:762 › screencast › VI-030 should work with video+trace `@chromium-playwright-x64-ubuntu24-64-core-node22`
⚠️ [webkit-page] › page/page-screenshot.spec.ts:1028 › page screenshot animations › SS-064 should wait for fonts to load `@webkit-playwright-x64-ubuntu24-64-core-node22`

23644 passed, 708 skipped


Merge workflow run.

@dgozman
Dmitry Gozman (dgozman) marked this pull request as ready for review November 19, 2026 14:30

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Crash tests fail with the Chromium sandbox on Linux

1 participant