Repository navigation
feat(firefox): roll to r1548 - #42747
Conversation
Test results for "tests 1"1 failed 9 flaky51718 passed, 1247 skipped Merge workflow run. |
🟢 The one failure is pre-existing — this PR is clearHi, I'm the Playwright bot and I triaged the failing CI run.
DetailsPre-existing flake / infra
Caused by this PR
The 9 flaky results all passed on retry and are outside the scope of this verdict. Triaged by the Playwright bot - agent run |
Test results for "MCP"2 failed 8562 passed, 1446 skipped Merge workflow run. |
🟢 All three failures are pre-existing — the roll is clearHi, I'm the Playwright bot and I triaged the failing CI runs. Both MCP failures are known flakes that fail with byte-identical errors on DetailsThis PR changes only the Firefox build: Pre-existing flake / infra
Triaged by the Playwright bot - agent run |
Test results for "tests 2"5 failed 29 flaky111373 passed, 4739 skipped Merge workflow run. |
🟢 Neither failure is caused by this rollHi, I'm the Playwright bot and I triaged the failing CI here. Both failing tests are Firefox-only, but neither traces back to r1548: the storage-state one is a known break that fails on DetailsThis PR only touches Pre-existing flake / infra
No failure in this report needs a change to the roll. Triaged by the Playwright bot - agent run |
…eed (daijro#1110) Gecko keeps a connection's notificationCallbacks, which Juggler sets to the NetworkRequest, until the connection closes. A finished request still held its PageNetwork, and through it the page's target and up to 100 MB of response bodies, so every closed page stayed in the parent process for as long as a connection it had opened (daijro#1107). Finished and redirected requests now release those references, as Playwright's Juggler does (microsoft/playwright#42747). The closed-page-released guard loads a page over HTTP/2, closes it, and checks through Marionette that a garbage collection frees its target and PageNetwork. It fails on the unfixed build every time. Closes daijro#1107 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…eed (#1110) Gecko keeps a connection's notificationCallbacks, which Juggler sets to the NetworkRequest, until the connection closes. A finished request still held its PageNetwork, and through it the page's target and up to 100 MB of response bodies, so every closed page stayed in the parent process for as long as a connection it had opened (#1107). Finished and redirected requests now release those references, as Playwright's Juggler does (microsoft/playwright#42747). The closed-page-released guard loads a page over HTTP/2, closes it, and checks through Marionette that a garbage collection frees its target and PageNetwork. It fails on the unfixed build every time. Closes #1107 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Browser build: https://github.com/microsoft/playwright-browsers/commit/2c149e66f5db026abc96f9dbbff922708b24c045. Build has full platform coverage - check that all tests pass there.