Skip to content

Linux_android_emu_vulkan_stable android_hardware_smoke_vulkan_tests is 2.00% flaky #189843

Closed

Activity

  1. added
    P0Critical issues such as a build break or regression
    c: flakeTests that sometimes, but not always, incorrectly pass
    on Jul 22, 2026
  2. andywolff commented on Jul 22, 2026

    @andywolff
    Contributor

    The flakes linked here look like issue #189079, platform view tests render a black screen. I recently merged PR #189151 to address this type of failure. That may have reduced the flakiness below 2%, we'll see after another ~50 builds or so. I don't think that PR completely solved the black screen issue, however. Sometimes the app can load in a bad state such that synchronization is not the problem. I have an experimental PR in progress which will detect such a state and attempt a restart.

  3. jmagman commented on Jul 27, 2026

    @jmagman
    Member

    I'm going to unsuppress this test in the tree so we notice if it starts flaking again. Thanks @andywolff!

  4. Piinks commented on Jul 27, 2026

    @Piinks
    Contributor

    Should we close this then if unsuppressed?

  5. andywolff commented on Aug 3, 2026

    @andywolff
    Contributor

    It looks like the flakiness level is still above 2%, can we suppress again this until after #190110 is merged? Sorry my first comment didn't make that preference clear

  6. Piinks commented on Aug 3, 2026

    @Piinks
    Contributor

    Marked suppressed! FYI - we all with write access have the ability to do so. :)

  7. andywolff commented on Aug 3, 2026

    @andywolff
    Contributor

    Ah, thank you, I didn't realize that I could do this. I'll unsuppress and update this issue when I determine it's ready.

  8. andywolff commented on Aug 5, 2026

    @andywolff
    Contributor

    My PR has merged and fluttergithubbot says this is down to 1% flakiness anyway, so I've unsuppressed and I'm closing this issue

  9. github-actions commented on Aug 19, 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.

  10. locked as resolved and limited conversation to collaborators on Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P0Critical issues such as a build break or regressionc: flakeTests that sometimes, but not always, incorrectly passteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions