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_emu android_engine_opengles_tests is 2.04% flaky #179673
The post-submit test builder Linux_android_emu android_engine_opengles_tests had a flaky ratio 2.04% for the past (up to) 100 commits, which is above our 2.00% threshold.
I suspect d143c41#diff-e2fc199ed8cf5317f4164deef1185196dfc0e02e3df37b34148e1bdf66adada9 is the cause here. The flakiness starts at that commit AFAICT, and it makes sense to me. Previously the call to jni_facade->MaybeResizeSurfaceView(...) was synchronous, but after the commit it is asynchonous. Probably the blocking behavior was important to these tests (i.e. rotate and then take screenshot) (cc @mboetger )
I suspect d143c41#diff-e2fc199ed8cf5317f4164deef1185196dfc0e02e3df37b34148e1bdf66adada9 is the cause here. The flakiness starts at that commit AFAICT, and it makes sense to me. Previously the call to jni_facade->MaybeResizeSurfaceView(...) was synchronous, but after the commit it is asynchonous. Probably the blocking behavior was important to these tests (i.e. rotate and then take screenshot) (cc @mboetger )
I was looking at this yesterday too. Will dig deeper.
I suspect d143c41#diff-e2fc199ed8cf5317f4164deef1185196dfc0e02e3df37b34148e1bdf66adada9 is the cause here. The flakiness starts at that commit AFAICT, and it makes sense to me. Previously the call to jni_facade->MaybeResizeSurfaceView(...) was synchronous, but after the commit it is asynchonous. Probably the blocking behavior was important to these tests (i.e. rotate and then take screenshot) (cc @mboetger )
I was looking at this yesterday too. Will dig deeper.
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
Piinks commentedon Dec 15, 2025
This did not get a team issue, added team-android to route to triage.
fluttergithubbot commentedon Dec 24, 2025
[prod pool] flaky ratio for the past (up to) 100 commits between 2025-12-17 and 2025-12-23 is 1.01%. Flaky number: 1; total number: 99.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_engine_opengles_tests/4778
Commit: a96687c
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_engine_opengles_tests/4778
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android_emu%20android_engine_opengles_tests
fluttergithubbot commentedon Dec 31, 2025
[prod pool] flaky ratio for the past (up to) 100 commits between 2025-12-18 and 2025-12-30 is 0.00%. Flaky number: 0; total number: 100.
fluttergithubbot commentedon Jan 7, 2026
[prod pool] flaky ratio for the past (up to) 100 commits between 2025-12-23 and 2026-01-06 is 0.00%. Flaky number: 0; total number: 100.
fluttergithubbot commentedon Jan 14, 2026
[prod pool] flaky ratio for the past (up to) 100 commits between 2026-01-07 and 2026-01-13 is 1.02%. Flaky number: 1; total number: 98.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_engine_opengles_tests/5036
Commit: 025911f
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_engine_opengles_tests/5036
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android_emu%20android_engine_opengles_tests
fluttergithubbot commentedon Jan 21, 2026
[prod pool] flaky ratio for the past (up to) 100 commits between 2026-01-13 and 2026-01-20 is 0.00%. Flaky number: 0; total number: 99.
fluttergithubbot commentedon Jan 28, 2026
[prod pool] flaky ratio for the past (up to) 100 commits between 2026-01-21 and 2026-01-27 is 2.15%. Flaky number: 2; total number: 93.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_engine_opengles_tests/5335
Commit: a132701
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_engine_opengles_tests/5335
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_engine_opengles_tests/5270
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android_emu%20android_engine_opengles_tests
12 remaining items
reidbaker commentedon Feb 10, 2026
@gmackall can you dig into this and try to figure out how we could get different aspect ratios?
gmackall commentedon Feb 10, 2026
I suspect d143c41#diff-e2fc199ed8cf5317f4164deef1185196dfc0e02e3df37b34148e1bdf66adada9 is the cause here. The flakiness starts at that commit AFAICT, and it makes sense to me. Previously the call to
jni_facade->MaybeResizeSurfaceView(...)was synchronous, but after the commit it is asynchonous. Probably the blocking behavior was important to these tests (i.e. rotate and then take screenshot) (cc @mboetger )mboetger commentedon Feb 10, 2026
mboetger commentedon Feb 10, 2026
Ensure resize listener is not added if content sizing is not turned on (
Ensure resize listener is not added if content sizing is not turned on (
[CP-stable]Ensure resize listener is not added if content sizing is n…
Ensure resize listener is not added if content sizing is not turned on (
github-actions commentedon Feb 25, 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.Ensure resize listener is not added if content sizing is not turned on (