Skip to content

Revert "fix: do not force swiftshader on chromium mac (#39129)"#39359

Merged
dgozman merged 1 commit intomicrosoft:mainfrom
dgozman:revert-6a6719e
Feb 24, 2026
Merged

Revert "fix: do not force swiftshader on chromium mac (#39129)"#39359
dgozman merged 1 commit intomicrosoft:mainfrom
dgozman:revert-6a6719e

Conversation

@dgozman
Copy link
Contributor

@dgozman dgozman commented Feb 23, 2026

This reverts commit 6a6719e.

The fix is now available in the latest chromium roll. Closes #38476.

@github-actions
Copy link
Contributor

Test results for "tests 1"

1 failed
❌ [playwright-test] › reporter.spec.ts:251 › merged › should not have internal error when steps are finished after timeout @macos-latest-node20

3 flaky ⚠️ [chromium-page] › page/page-request-continue.spec.ts:754 › propagate headers cross origin redirect after interception `@chromium-ubuntu-22.04-node24`
⚠️ [firefox-page] › page/page-wait-for-function.spec.ts:104 › should work with strict CSP policy `@firefox-ubuntu-22.04-node20`
⚠️ [webkit-page] › page/page-network-request.spec.ts:288 › should parse the data if content-type is application/x-www-form-urlencoded `@webkit-ubuntu-22.04-node20`

38568 passed, 843 skipped


Merge workflow run.

@github-actions
Copy link
Contributor

Test results for "MCP"

1 failed
❌ [chrome] › mcp/launch.spec.ts:21 › test reopen browser @mcp-macos-15

4895 passed, 135 skipped


Merge workflow run.

@dgozman dgozman merged commit 331dc03 into microsoft:main Feb 24, 2026
31 of 34 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.

[Internal]: do not force swiftshader on chromium mac

2 participants