You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Flutter Packages Web shards timing out with no clear cause. #191149
breakage; unable to contribute or trigger builds will no workarounds
inconvenient workarounds exist, but significant effort required
needed for a Flutter team-wide priority (already agreed upon)
nice-to-have; none of the above
What do you need help with
flutter/packages#12465
This pr should pass all tests, but the web shards are timing out after 60 minutes while the logs stop after 1 -3 minutes. I assume something is crashing, but it happens at different times and tests every run. The logs and output show nothing useful.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
tarrinneal commentedon Aug 15, 2026
It seems to be inconsistent. I managed to get the tests to pass after a many different iterations and reruns.
https://flutter-dashboard.appspot.com/#/presubmit?repo=packages&pr=12465&sha=0e1a6cdba8a8729f9a2e7fdf204b07d781ebc8cc&job=Linux_android%20android_platform_tests_shard_1%20master
jtmcdole commentedon Aug 17, 2026
The logging stops after this.
team-infrais not going to be the team to help you figure this out.tarrinneal commentedon Aug 17, 2026
the logging stops at a different place every time the tests run, it's not a specific test that is causing the crash/timeout
tarrinneal commentedon Aug 17, 2026
it's being looked into by the web team flutter/packages#12486
Fix chrome 145 web tests (#12486)
github-actions commentedon Sep 2, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.