feat(firefox): roll to r1544 - #42631
Conversation
Test results for "tests 1"6 flaky51411 passed, 1240 skipped Merge workflow run. |
Test results for "MCP"3 failed 8345 passed, 1376 skipped Merge workflow run. |
🟢 No real failures — all three are pre-existing MCP flakesHi, I'm the Playwright bot and I took a look at the CI on this Firefox roll (r1544). The "tests 1" report has 0 failures (6 flaky, all retried green). The only reds are 3 MCP tests, and every one of them fails on SHAs this roll can't be responsible for — two of them aren't even Firefox. The roll changes the Firefox binary only; nothing here points back to it. The PR is clear. DetailsOverall: this Firefox roll only bumps the Firefox browser build. Two of the three failures are on Chrome/Edge — outside anything the roll touches — and the one Firefox failure flakes on unrelated Pre-existing flake / infra
Triaged by the Playwright bot - agent run |
Test results for "tests 2"3 failed 30 flaky110762 passed, 4725 skipped Merge workflow run. |
🟢 No real failures from this roll — three pre-existing Chromium/Android issuesHi, I'm the Playwright bot and I took a look at the CI on this Firefox roll (r1544). This PR swaps the Firefox binary only — the diff is entirely DetailsOverall: a Firefox binary bump can't reach a Chromium CDP/OOPIF path or an Android click test. Every failure below is reproduced off this PR — on Pre-existing flake / infra
Triaged by the Playwright bot - agent run |
microsoft/playwright#42631 is on @next, not 1.63.0. Frontend CT stays on 1.62.1 because experimental-ct-react has no matching 1.64 package. Co-authored-by: Max Schmitt <max@schmitt.mx>
Browser build: https://github.com/microsoft/playwright-browsers/commit/50445f32fd98c5e19d1fdd3ee37b8e7af336bdda. Build has full platform coverage - check that all tests pass there.
References #42565.