Repository navigation
Windows_arm64 plugin_test_windows is 2.11% flaky #163122
Description
The post-submit test builder Windows_arm64 plugin_test_windows had a flaky ratio 2.11% 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_arm64%20plugin_test_windows/5178
Commit: 9438fd4
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows_arm64%20plugin_test_windows/5178
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows_arm64%20plugin_test_windows/5146
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Windows_arm64%20plugin_test_windows
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
ergosarapu commentedon Feb 17, 2025
@loic-sharma Can you please check if this is caused by the Windows Defender issue mentioned in #145110?
Marks Windows_arm64 plugin_test_windows to be flaky (#163123)
loic-sharma commentedon Feb 18, 2025
@ergosarapu Unfortunately I only reduced the timeout as I was the gardener at that time, the Windows Defender identification was done by someone else.
The test in question has been labeled as flaky, so it should no longer close the tree. I'll unassign myself as I don't have the time to investigate Windows Arm64 issue currently.
ergosarapu commentedon Feb 19, 2025
@keyonghan Is this something that you can help with? I noticed you were reviewer in an earlier issue.
Piinks commentedon Feb 25, 2025
Hey @ergosarapu keyonghan likely won't be working on this. They are on another team now.
fluttergithubbot commentedon Feb 26, 2025
[prod pool] flaky ratio for the past (up to) 100 commits between 2025-02-12 and 2025-02-18 is 0.00%. Flaky number: 0; total number: 87.
fluttergithubbot commentedon Feb 26, 2025
[staging pool] flaky ratio for the past (up to) 100 commits between 2025-02-19 and 2025-02-25 is 0.00%. Flaky number: 0; total number: 100.
ergosarapu commentedon Mar 4, 2025
The root cause of why
flutter testcommand times out, stays unclear.Since it is not happening in staging, my suggestion is to remove bringup. If the timeout occurs again, someone with access to the bot could debug what is happening inside the bot.
fluttergithubbot commentedon Mar 5, 2025
[prod pool] flaky ratio for the past (up to) 100 commits between 2025-02-12 and 2025-02-18 is 0.00%. Flaky number: 0; total number: 77.
fluttergithubbot commentedon Mar 5, 2025
[staging pool] flaky ratio for the past (up to) 100 commits between 2025-02-27 and 2025-03-04 is 0.00%. Flaky number: 0; total number: 100.
Piinks commentedon Mar 5, 2025
Thanks @ergosarapu! This is no longer on bringup, so I am going to close this issue and let the bot file a new one with details to investigate if it recurs. Thank you!
github-actions commentedon Mar 20, 2025
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.