Repository navigation
Windows plugin_test is 2.00% flaky #174116
Description
The post-submit test builder Windows plugin_test had a flaky ratio 2.00% for the past (up to) 100 commits, which is above our 2.00% threshold.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20plugin_test/16247
Commit: 138a60c
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20plugin_test/16247
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20plugin_test/16245
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Windows%20plugin_test
Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Activity
stuartmorgan-g commentedon Aug 20, 2025
Looks like building and running the Android app several times is timing out the ~30 min per-test timeout that IIRC all tests have (regardless of the overall task timeout, which is 60 mins for this task). It looks like when it passes it often takes about 20 minutes, but can go up to almost 30.
Routing to
team-androidto see if this build time seems reasonable, in which case we probably just need to split these tests into a couple of separate tasks, or if we think there's a bug that's causing build times to vary so much.Marks Windows plugin_test to be flaky (#174117)
[Android] Break up plugin_test integration tests (#174728)
Marks Windows plugin_test to be flaky (flutter#174117)
[Android] Break up plugin_test integration tests (flutter#174728)
Marks Windows plugin_test to be flaky (flutter#174117)
Marks Windows plugin_test to be flaky (flutter#174117)
[Android] Break up plugin_test integration tests (flutter#174728)
Marks Windows plugin_test to be flaky (flutter#174117)
[Android] Break up plugin_test integration tests (flutter#174728)
flutter-triage-bot commentedon Dec 29, 2025
This issue is assigned to @camsim99 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!
flutter-triage-bot commentedon Mar 17, 2026
This issue was assigned to @camsim99 but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
gmackall commentedon Mar 17, 2026
Has not flaked in the last 100 runs, closing, bot can re open if it flakes again
github-actions commentedon Mar 31, 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.