Sitelet https://github.com/flutter/flutter/pull/189521
Skip to content

[web] Remove per-launch browser console listener from test harness - #189521

Closed
flutter-zl wants to merge 2 commits into
flutter:masterfrom
flutter-zl:issue_189275_console_experiment
Closed

flutter-zl wants to merge 2 commits into
flutter:masterfrom
flutter-zl:issue_189275_console_experiment

Conversation

@flutter-zl

Copy link
Copy Markdown
Contributor

Draft, do not merge. Measurement only for #189275. Removes the per-launch browser console listener added in #182861 to see whether it recovers meaningful time on the web test shards. If it does, the landable version would gate the listener behind verbose mode rather than delete it.

@github-actions github-actions Bot added the tool Affects the "flutter" command-line tool. See also t: labels. label Jul 15, 2026
@flutter-zl
flutter-zl marked this pull request as ready for review July 15, 2026 18:52

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request removes the unused webkit_inspection_protocol import and deletes the asynchronous block in BrowserManager that connected to the Chrome tab to listen for console API calls and exceptions. There are no review comments, and I have no feedback to provide.

@flutter-zl flutter-zl added the CICD Run CI/CD label Jul 15, 2026
@flutter-zl

Copy link
Copy Markdown
Contributor Author

Update on the cause. Short version: these shards are not slowly running over their time limit, they are getting stuck.

What I found on web_canvaskit_tests_6:

  • The failure looks the same on master and on my test PR: the shard runs for exactly 60 minutes doing nothing, then gets killed by the timeout.
  • Over the last 30 master commits it got stuck 4 times, each time rescued by an automatic retry. So postsubmit stays green, but every flake burns a wasted 60 minute run.
  • In the logs it always freezes at the same moment: while loading a new test file, the browser just stops responding mid-load. It is a different, random file each time, so it is not one bad test.

Why this matters: because the shard is hanging, not running slow, bumping the timeout or adding shards will not fix it. It will just hang longer, or hang somewhere else. The real fix is figuring out why Chrome 145 sometimes freezes while loading a test.

Side note: I tried removing the console listener the roll added (#189521) in case it was the cost. It is not, master still has that listener and hangs the same way, so that is ruled out.

@harryterkelsen @kevmoo any idea what in Chrome 145 headless could make it randomly freeze while loading a test?

@flutter-zl flutter-zl closed this Jul 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CICD Run CI/CD tool Affects the "flutter" command-line tool. See also t: labels.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant