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
Windows framework_tests_misc flakes on live_widget_controller_test #97165
/cc @HansMuller Could you help take a further look? We are scanning flakes in shards tests (which contains many unit/integration tests), and want to either fix or skip corresponding flaky tests to try achieving 0 flakes from them. Thanks!
This issue is assigned but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
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
keyonghan commentedon Jan 25, 2022
/cc @HansMuller Could you help take a further look? We are scanning flakes in shards tests (which contains many unit/integration tests), and want to either fix or skip corresponding flaky tests to try achieving 0 flakes from them. Thanks!
keyonghan commentedon May 6, 2022
This is still happening: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20framework_tests_misc/4579/overview
HansMuller commentedon Jan 4, 2023
@pdblasi-google, @keyonghan - perhaps this is no longer happening?
flutter-triage-bot commentedon Jul 9, 2023
This issue is assigned but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
goderbauer commentedon Aug 15, 2023
Closing this as there have been no further reports.
github-actions commentedon Aug 29, 2023
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.