Skip to content

Linux_android_emu android_engine_opengles_tests is 2.04% flaky #179673

Closed

Activity

  1. added
    P0Critical issues such as a build break or regression
    c: flakeTests that sometimes, but not always, incorrectly pass
    on Dec 10, 2025
  2. Piinks commented on Dec 15, 2025

    @Piinks
    Contributor

    This did not get a team issue, added team-android to route to triage.

  3. added
    P1High-priority issues at the top of the work list
    triaged-androidTriaged by Android platform team
    and removed
    P0Critical issues such as a build break or regression
    on Dec 16, 2025
  4. fluttergithubbot commented on Dec 31, 2025

    @fluttergithubbot
    ContributorAuthor

    [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.

  5. fluttergithubbot commented on Jan 7, 2026

    @fluttergithubbot
    ContributorAuthor

    [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.

  6. fluttergithubbot commented on Jan 21, 2026

    @fluttergithubbot
    ContributorAuthor

    [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.

  7. removed
    P1High-priority issues at the top of the work list
    on Jan 28, 2026
  8. 12 remaining items

  9. reidbaker commented on Feb 10, 2026

    @reidbaker
    Member

    @gmackall can you dig into this and try to figure out how we could get different aspect ratios?

  10. gmackall commented on Feb 10, 2026

    @gmackall
    Member

    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 )

  11. mboetger commented on Feb 10, 2026

    @mboetger
    Contributor

    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.

  12. mboetger commented on Feb 10, 2026

    @mboetger
    Contributor

    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.

  13. self-assigned this
    on Feb 10, 2026
  14. added a commit that references this issue on Feb 11, 2026
    b9febd8
  15. added a commit that references this issue on Feb 12, 2026
    eeedb9a
  16. added a commit that references this issue on Feb 19, 2026
    1752545
  17. github-actions commented on Feb 25, 2026

    @github-actions

    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.

  18. locked as resolved and limited conversation to collaborators on Feb 25, 2026
  19. added a commit that references this issue on Mar 26, 2026
    849f158
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P1High-priority issues at the top of the work listc: flakeTests that sometimes, but not always, incorrectly passteam-androidOwned by Android platform team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions