Repository navigation
devops: pin exact Node.js version in Docker images - #44156
Conversation
The version lives in the playwright-core package.json as playwright.nodeVersion. Docker images install that exact version from nodejs.org instead of the latest NodeSource build of a major.
This comment has been minimized.
This comment has been minimized.
🟢 Both failures already occur on mainHi, I'm the Playwright bot. I checked the failed run: neither failure was caused by this PR. DetailsThe PR changes Docker Node.js installation and version metadata, not the JUnit reporter or these tests. The failed Windows job still uses Node.js 22 through Pre-existing failure
Checked the failures on Linux by the Playwright bot - agent run |
This comment has been minimized.
This comment has been minimized.
🟢 All three MCP failures already occur on mainHi, I'm the Playwright bot. I checked the failed MCP run: these failures were not caused by this PR. DetailsThe PR changes Docker Node.js installation and version metadata. The failed Ubuntu Chrome job uses Pre-existing failures All three
This confirms pre-existing crash-recovery failures, not that they are intermittent flakes. The earlier JUnit failures already have a separate verdict above. Checked the failures on Linux by the Playwright bot - agent run |
Remove playwright.nodeVersion from the playwright-core package.json. The roll script writes the exact version into the Dockerfiles.
Test results for "MCP"3 failed 5232 passed, 631 skipped Merge workflow run. |
Test results for "tests 1"2 failed 1 flaky23643 passed, 716 skipped Merge workflow run. |
🟢 All five failures already occur on mainHi, I'm the Playwright bot. I checked MCP run 43971153260 and tests 1 run 43971153371 at DetailsThe PR changes only three Dockerfiles and the Node.js roll script. Both failed jobs use Node.js 22 through Pre-existing failures All three Ubuntu Chrome crash-recovery tests fail identically in main run 43957125480, commit
The Windows JUnit failure also repeats at this head:
These are confirmed pre-existing failures; the evidence does not establish that they are intermittent flakes. Checked the failures on Linux by the Playwright bot - agent run |
🟢 Both failures are pre-existing, not caused by this PRHi, I'm the Playwright bot. I checked tests 1 run 43971153371 at DetailsThe only failed job is Windows Test Runner, using Node.js 22 through Pre-existing failures
These are pre-existing test failures, not established intermittent flakes. The Selenium test passed on retry and is not an outstanding failure. This pass verified the diff, workflow configuration and failed-job identity. Fresh log access was blocked by GitHub tool errors and REST permission checks; the exact error comparison above comes from the earlier investigation. Checked the failures on Linux by the Playwright bot - agent run |
1aa8478
into
microsoft:main
Summary
ARG NODE_VERSION=26.13.1), not only the major version.nodejs.org/dist(with a checksum check) and no longer use NodeSource. Node.js moves from/usr/binto/usr/local/bin.update-playwright-node.mjsnow rolls the full version.