Uh oh!
There was an error while loading. Please reload this page.
chore(utils): always use setImmediate in makeWaitForNextTask - #42456
Conversation
Node < 11 and the Electron setImmediate bug (electron/electron#28261) are no longer relevant now that Node 20+ is required and the Electron issue has been fixed.
This comment has been minimized.
This comment has been minimized.
Test results for "tests 1"1 failed 8 flaky51273 passed, 1241 skipped Merge workflow run. |
Test results for "MCP"1 failed 8304 passed, 1367 skipped Merge workflow run. |
🟢 CI is clear — both hard failures are pre-existing flakesHi, I'm the Playwright bot and I took a look at the failing CI. Neither hard failure traces to this PR: both fail on the same test on unrelated PRs. This change swaps DetailsOverall: the diff only touches Pre-existing flake / infra
Triaged by the Playwright bot - agent run |
Hi, I'm the Playwright bot and I took a first look at the failing CI. 🟢 CI is clear — both real failures are pre-existing flakesThe two red tests fail the same way on unrelated PRs, and this change is a no-op on the bots where they failed: DetailsOverall: the diff only changes behaviour under Node < 11 (obsolete) and Electron; on every standard CI bot it's identical to the old code. Electron jobs passed. The two failures below both land on standard bots, so the PR can't be the cause — and the history confirms they flake on their own. Pre-existing flake / infra
Not triaged The 8 "flaky" entries in the report (video screencast, third-party cookies, Triaged by the Playwright bot - agent run |
Test results for "tests 2"31 flaky110484 passed, 4723 skipped Merge workflow run. |
de214f4
into
microsoft:mainUh oh!
There was an error while loading. Please reload this page.
Summary
setImmediatefrommakeWaitForNextTask: the Node < 11 microtask ordering workaround is obsolete now that Node 20+ is required, and the ElectronsetTimeout(0)fallback is no longer needed since [Bug]: setImmediate does not make a new task electron/electron#28261 has been fixed.