Linux_android new_gallery__crane_perf is 2.06% flaky
The post-submit test builder Linux_android new_gallery__crane_perf had a flaky ratio 2.06% 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/Linux_android%20new_gallery__crane_perf/6561 Commit: https://github.com/flutter/flutter/commit/577ad2ee8a0de438d06b7fb6829901701d064782
Flaky builds: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20new_gallery__crane_perf/6561 https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20new_gallery__crane_perf/6488
Recent test runs: https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android%20new_gallery__crane_perf
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).
Both of these look like the device disappeared, but more so in 6488. Routing to infra.
We need a method to the device class in flutter/flutter to wait for the device to be available after force removing apps.
[prod pool] current flaky ratio for the past (up to) 100 commits is 0.00%. Flaky number: 0; total number: 97.
https://github.com/flutter/flutter/issues/120802
The fix to address this flake will be done in this work: https://github.com/flutter/flutter/issues/121420
[prod pool] current flaky ratio for the past (up to) 100 commits is 0.00%. Flaky number: 0; total number: 99.
Closing in favor of https://github.com/flutter/flutter/issues/121420
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.