[web] Roll Chrome to 145 (framework)#182861
Conversation
44c1e8c to
1a0f0d2
Compare
|
Greetings from stale PR triage! 👋 |
adf6309 to
6b20390
Compare
Add support for detecting ARM architecture on macOS.
47db658 to
442f524
Compare
There was a problem hiding this comment.
Code Review
This pull request updates the Chrome and Chromedriver dependencies to version 145.0.7632.117 across CI configurations and introduces the --password-store=basic and --use-mock-keychain flags to prevent credential store prompts during testing. Additionally, on ARM macOS, the logic forcing native ARM launch is removed in favor of appending the --use-angle=metal flag to bypass SwiftShader limitations. Review feedback suggests restricting this new flag to headless mode only, as the software rendering issue with SwiftShader specifically impacts headless execution.
…orkaround to headless mode - Restrict --use-mock-keychain to macOS platforms. - Restrict the --use-angle=metal SwiftShader workaround on ARM macOS to headless executions. - Update Chrome launcher tests to validate headed, headless, and cross-platform behaviors.
|
@mdebbar – did some more tweaks on top of your tweaks and pushed. PTAL! |
…vent CanvasKit hangs Under Chrome 145+, passing --disable-dev-shm-usage unconditionally forces Chrome to write all shared memory IPC buffers to /tmp. While this is required for Wasm/SkWasm multi-threaded tests to avoid crashing on the 64MB /dev/shm limit in containerized environments, it degrades disk IPC performance and causes standard CanvasKit tests to hang/timeout on CI. Restores the previous behavior where --disable-dev-shm-usage is passed only when useWasm is true. CONV=b0179f43-b48a-45ed-8b0f-df9a00890861 TAG=agy
# Conflicts: # .ci.yaml # packages/flutter_tools/test/commands.shard/hermetic/build_macos_test.dart
Increase reloadRestartTimeout and log check timeouts to 30s to reduce flakiness on CI. Format modified files to resolve linux_unopt failures.
This ignores the lint for the debug print we added to capture browser logs. Both should be reverted before merging if CI goes green.
Resolve template change detection failure by formatting the template to match the formatted implementation file.
Clean up the PR by reverting whitespace-only, formatting-only, and other unrelated changes in 17 files to match origin/master.
harryterkelsen
left a comment
There was a problem hiding this comment.
Thanks, Kevin! A couple more small things I missed on my first pass
|
autosubmit label was removed for flutter/flutter/182861, because - The status or check suite Google testing has failed. Please fix the issues identified (or deflake) before re-applying this label. |
No description provided.