Repository navigation
Linux_android_emu android_hardware_smoke_opengles_tests is 2.00% flaky #191348
Description
The post-submit test builder Linux_android_emu android_hardware_smoke_opengles_tests 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/Linux_android_emu%20android_hardware_smoke_opengles_tests/659
Commit: 5a0a353
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_hardware_smoke_opengles_tests/659
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_hardware_smoke_opengles_tests/605
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
andywolff commentedon Aug 19, 2026
Both of the failures listed are blank screenshots for platform view tests. Analyzing the history of all andorid_hardware_smoke_test shards across envs, it looks like the detection and retries I introduced in PR #190110 were not enough to bring the flakiness below 2%. I analyzed the history, and it appears that it is sufficiently detecting the blank screenshots and attempting to retry, but the failure mode remains the same on subsequent retries. So either it starts in a bad state and all retries fail, or it succeeds the first time. I'll think about alternative strategies. Let's leave this suppressed for now
android_hardware_smoke_test: Improve reliability (flutter#191374)
andywolff commentedon Aug 21, 2026
I merged another attempted improvement, I'll check back in next week to see if it had the desired effect
andywolff commentedon Aug 24, 2026
It looks like that improvement was fairly successful, I'm going to unsuppress and close this issue.
github-actions commentedon Sep 7, 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.Fix android_hardware_smoke_test retry mechanisms (flutter#195708)