[Dmitry Gozman (dgozman)]

No description provided.

[microsoft-playwright-automation]

🔴 Two failures caused by the Chromium roll

Hi, I'm the Playwright bot. I checked the five failures: two need updated CSS expectations; the three Chrome crash failures also occur on main.

Details and suggested fix

Covers MCP run 43434813116 for head 06440a0db25b.

Caused by this PR

• [chromium] mcp/cli-devtools.spec.ts:397 — highlight --style, and mcp/devtools.spec.ts:42 — browser_highlight with style. The roll from Chromium 158.0.8127.18 to 159.0.8154.6 changes el.style.outline from rgb(255, 0, 0) solid 3px to 3px solid rgb(255, 0, 0). The highlight is visible and the background color matches; only the outline string order differs. Both tests passed on the base commit's MCP run, and each has 723 passing Ubuntu runs with no failures in the earlier recorded history. Suggested fix: in both tests, assert outlineWidth, outlineStyle, and outlineColor separately instead of the shorthand's string order.

Pre-existing flake / infra

• [chrome] mcp/crash.spec.ts:31, :58, :79 — all three crash-recovery tests fail identically on main at 8534271f0413: the reset/log check times out; both tab-list checks time out with Not connected. Each also failed in 29 earlier Ubuntu Chrome runs. These are persistent pre-existing failures, not evidence of an intermittent flake. The Chrome project uses the installed Chrome channel, not the bundled Chromium changed here.

_{Checked the failures on Linux by the Playwright bot - agent run}

[microsoft-playwright-automation]

🔴 One test failure caused by the Chromium roll, on all three platforms

Hi, I'm the Playwright bot. I checked the tests 1 failures: the watch-icon test needs updated CSS expectations, not a UI fix.

Evidence and suggested fix

Covers tests 1 run 43434813211 at 06440a0db25b. The MCP failures already have a separate verdict.

Caused by this PR

• [playwright-test] › ui-mode-test-watch.spec.ts:326 › should have watch icon highlighted when a test is focused and watch on the test is enabled — one group, failing on Linux, macOS, and Windows. All four attempts on each platform fail at line 341 with the same difference:

  Expected: "rgb(255, 255, 255) solid 1px"
  Received: "1px solid rgb(255, 255, 255)"
  

The roll from Chromium 158.0.8127.18 to 159.0.8154.6 changes the order of the computed outline string. Its width, style, and color are unchanged. The corresponding test-runner jobs succeeded on the base commit, 8534271f0413.

Suggested fix: assert outline-width, outline-style, and outline-color separately. Update the two negative outline assertions in this test too: comparison against the old string order can now pass even when the white outline is present.

The two tests reported as flaky passed on retry and are not additional failures.

_{Checked the failures on Linux by the Playwright bot - agent run}

[github-actions]

Test results for "MCP"

3 failed
❌ [chrome] › mcp/crash.spec.ts:31 › crash recovery › reports the navigation error, then resets and logs the crash @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:58 › crash recovery › lists only one tab @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:79 › crash recovery › marks non-current crashed tab in the tab list @mcp-ubuntu-latest-chrome

5232 passed, 631 skipped

---

Merge workflow run.

[github-actions]

Test results for "tests 1"

2 flaky

⚠️ [installation tests] › connect-to-selenium.spec.ts:20 › connect to selenium `@package-installations-ubuntu-latest`
⚠️ [chromium-library] › library/video.spec.ts:762 › screencast › VI-030 should work with video+trace `@chromium-playwright-x64-ubuntu24-64-core-node22`

23638 passed, 716 skipped

---

Merge workflow run.

[microsoft-playwright-automation]

🟢 All three MCP failures predate this PR

Hi, I'm the Playwright bot. I checked the latest MCP run: the three Chrome crash-recovery failures also occur on main; the earlier Chromium outline failures are gone.

Evidence for each failure

Covers MCP run 43443904854 at eecedbe69c2ae4bdbff554d02d0a90fa4b2d5a28, summarized in the latest merged report.

Pre-existing flake / infra

All three tests fail identically in the Ubuntu Chrome job on main at 8534271f0413, before this PR:

• [chrome] mcp/crash.spec.ts:31 — reports the navigation error, then resets and logs the crash: the reset/log check at line 48 exceeds the 30-second test timeout in both runs.
• [chrome] mcp/crash.spec.ts:58 — lists only one tab: the tab-list call at line 71 times out with Not connected in both runs.
• [chrome] mcp/crash.spec.ts:79 — marks non-current crashed tab in the tab list: the tab-list call at line 93 times out with Not connected in both runs.

These are confirmed pre-existing failures, not evidence of intermittent flakes. The Chrome project uses the installed Chrome channel, not the bundled Chromium updated here. The PR does not change crash recovery or its fixtures.

The two MCP highlight tests now assert outline width, style, and color separately and are no longer reported as failures. No remaining MCP failure is caused by this PR.

_{Checked the failures on Linux by the Playwright bot - agent run}