Skip to content

cherry-pick(#43679): fix(docker): use latest stable Chrome for Testing - #43828

Merged
Dmitry Gozman (dgozman) merged 1 commit into
microsoft:release-1.64from
dgozman:r1.64-256c530
Oct 31, 2026
Merged

Dmitry Gozman (dgozman) merged 1 commit into
microsoft:release-1.64from
dgozman:r1.64-256c530

Conversation

@dgozman

Copy link
Copy Markdown
Collaborator

No description provided.

…or Testing and Node.js LTS

Co-authored-by: microsoft-playwright-automation[bot] <203992400+microsoft-playwright-automation[bot]@users.noreply.github.com>
Co-authored-by: Dmitry Gozman <dgozman@gmail.com>
@github-actions

Copy link
Copy Markdown
Contributor

Test results for "tests 1"

4 failed
❌ [chromium-page] › page/page-network-sizes.spec.ts:78 › should have the correct responseBodySize for chunked request @chromium-ubuntu-22.04-node24
❌ [default] › problems.spec.ts:19 › should list tests on expand @vscode-extension
❌ [default-reuse] › problems.spec.ts:19 › should list tests on expand @vscode-extension
❌ [default-trace] › problems.spec.ts:19 › should list tests on expand @vscode-extension

5 flaky ⚠️ [chromium-library] › library/webmcp.spec.ts:216 › should scope tools to their frame `@frozen-time-library-chromium-linux`
⚠️ [firefox-library] › library/browsercontext-cookies-third-party.spec.ts:257 › third party 'Partitioned;' cookies `@firefox-ubuntu-22.04-node20`
⚠️ [firefox-library] › library/browsercontext-cookies-third-party.spec.ts:470 › top level 'Partitioned;' cookie and same origin iframe `@firefox-ubuntu-22.04-node20`
⚠️ [webkit-page] › page/page-set-input-files.spec.ts:38 › should upload a folder `@webkit-ubuntu-22.04-node20`
⚠️ [playwright-test] › ui-mode-test-watch.spec.ts:185 › should watch new file `@ubuntu-latest-node26`

52886 passed, 1270 skipped


Merge workflow run.

@github-actions

Copy link
Copy Markdown
Contributor

Test results for "MCP"

3 failed
❌ [firefox] › mcp/annotate.spec.ts:349 › should annotate when context has no fixed viewport @mcp-windows-latest-firefox
❌ [firefox] › mcp/annotate.spec.ts:386 › should cancel browser_annotate when the MCP request is aborted @mcp-windows-latest-firefox
❌ [firefox] › mcp/annotate.spec.ts:446 › should switch screencast to -s session on show --annotate @mcp-windows-latest-firefox

9045 passed, 1495 skipped


Merge workflow run.

@github-actions

Copy link
Copy Markdown
Contributor

🟢 No failures look caused by this PR

Hi, I'm the Playwright bot. I checked all seven failures for head f115f943 (CI merge a70bb237): four match failures on an independent release PR, and three are confirmed pre-existing flakes.

Details

This PR only changes Docker packaging: utils/docker/build.sh and its new Chromium-version updater. None of the failing jobs runs that script; all six Docker test jobs passed. I refreshed the aggregated results database before checking test history.

Pre-existing failures / CI compatibility

  • Chromium, Ubuntu 22.04, Node 24: [chromium-page] › page/page-network-sizes.spec.ts:78 › should have the correct responseBodySize for chunked request reports 5113 instead of 5175 on all four attempts. The database records the identical test, bot and assertion failing on all four attempts in #43829's run, merge SHA 7c11c6e9. This is a repeatable failure outside this PR, not evidence of an intermittent flake.

  • VS Code extension: problems.spec.ts:19 › should list tests on expand fails in default, default-reuse and default-trace: the diagnostic starts at character 7, while the assertion expects 8. All three have the identical mismatch in #43829's extension job. Both jobs tested extension revision 1ed12654. This suite is absent from the results database, so this finding comes from the job logs; I am not calling it a flake.

#43829 shares base 0915b2e9, changes only Dockerfiles, and does not contain this PR's changes. Its matching failures confirm that these four failures are unrelated.

Confirmed pre-existing flakes — Windows Firefox MCP

All three tests in [firefox] › mcp/annotate.spec.ts have both passes and failures on the same Windows Firefox bot outside this PR. Counts below are final results per workflow run attempt, excluding #43828.

Test Passed / failed Prior failure
:349 › should annotate when context has no fixed viewport 284 / 1 #43252, attempt 2, SHA f76ba1f2: same dashboard visibility timeout and MCP connection closure.
:386 › should cancel browser_annotate when the MCP request is aborted 282 / 3 main run, SHA b536a638: same dashboard visibility timeout.
:446 › should switch screencast to -s session on show --annotate 257 / 28 main run, SHA b536a638: also times out waiting for Session second.

Triaged by the Playwright bot - agent run

@github-actions

Copy link
Copy Markdown
Contributor

🟢 CI failures are not caused by this PR

Hi, I'm the Playwright bot. I checked all seven failures against the PR diff and CI history; each has a matching failure outside this PR.

Details

Checked head f115f943 (CI merge a70bb237). The diff only changes Docker image packaging. The failing jobs do not run the changed build script and still install the pinned browsers; all six Docker checks passed.

Pre-existing test failures

  • Chromium / Node.js 24: [chromium-page] › page/page-network-sizes.spec.ts:78 › should have the correct responseBodySize for chunked request reports 5113 instead of 5175 on all four attempts. The refreshed results database shows the identical mismatch on the same bot in independent PR cherry-pick(#43478): chore: roll driver/Dockerfile to recent Node.js LTS version #43829, merge 7c11c6e (job). That PR has the same base and does not contain this change. This is not a Docker browser update leaking into the library tests.

  • VS Code: problems.spec.ts:19 › should list tests on expand fails in default, default-reuse, and default-trace: the diagnostic starts at character 7, while the test expects 8. All three already failed identically on this PR's exact base, 0915b2e9, on October 15 (base job). These tests are absent from the results database, so this comparison uses the job logs.

Pre-existing flakes — Windows Firefox MCP

The refreshed database confirms each exact [firefox] › mcp/annotate.spec.ts test failing on other commits on the same Windows bot, as well as passing on base 0915b2e9 (base run):

  • :349 › should annotate when context has no fixed viewport — annotation dashboard visibility timeout, also seen in fix(mcp): race browser_navigate_back and forward against modal states #43252 at f76ba1f2 (run, attempt 2).
  • :386 › should cancel browser_annotate when the MCP request is aborted — the same dashboard visibility timeout on main at b536a638 (run).
  • :446 › should switch screencast to -s session on show --annotate — times out waiting for Session second; the same session-switch assertion also failed on main at b536a638 (run).

Triaged by the Playwright bot - agent run

@dgozman
Dmitry Gozman (dgozman) merged commit 4044cb7 into microsoft:release-1.64 Oct 31, 2026
46 of 49 checks passed
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.

2 participants