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
Linux_android spell_check_test is 5.10% flaky #111569
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
Hixie commentedon Sep 20, 2022
@camsim99 did the PR above fix the flakiness?
camsim99 commentedon Sep 21, 2022
No, but the one linked above should!
fluttergithubbot commentedon Sep 28, 2022
[staging pool] current flaky ratio for the past (up to) 100 commits is 6.00%. Flaky number: 6; total number: 100.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1439
Commit: 7ce121f
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1439
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1423
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1420
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1406
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1377
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1351
https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_android%20spell_check_test/1350
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android%20spell_check_test
justinmc commentedon Oct 4, 2022
#112109 has been merged, but we should double check that it does indeed improve the flakiness.
github-actions commentedon Oct 18, 2022
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.