Windows gradle_plugin_bundle_test is 2.02% flaky

[fluttergithubbot]

The post-submit test builder Windows gradle_plugin_bundle_test had a flaky ratio 2.02% 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%20gradle_plugin_bundle_test/18681
Commit: f6c8cc3

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20gradle_plugin_bundle_test/18681
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows%20gradle_plugin_bundle_test/18609

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Windows%20gradle_plugin_bundle_test

Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).

[stuartmorgan]

I can't tell what one of these failures was, but the other was a network error downloading Flutter artifacts. Given that, the test itself doesn't reach the flake threshold.

[goderbauer]

(triage) @stuartmorgan Should we close this issue then based on your last message (or lower the priority)?

[github-actions]

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.