Linux_android_emu android_display_cutout is 4.17% flaky #181900

Activity

1. fluttergithubbot

   assigned

   reidbaker

   on Feb 4, 2026
2. fluttergithubbot

   added

   P0Critical issues such as a build break or regressionCritical issues such as a build break or regression

   c: flakeTests that sometimes, but not always, incorrectly passTests that sometimes, but not always, incorrectly pass

   on Feb 4, 2026
3. Piinks commented on Feb 9, 2026

   

   Piinks

   on Feb 9, 2026

   Contributor

   More actions

   This is ~40 minutes run time, I will approve the PR to put it on bring up for now.
4. github-merge-queue

   added a commit that references this issue on Feb 10, 2026

   Marks Linux_android_emu android_display_cutout to be flaky (#181901)

   ...

   885da00
5. reidbaker

   added

   P2Important issues not at the top of the work listImportant issues not at the top of the work list

   fyi-infraFor the attention of Infrastructure teamFor the attention of Infrastructure team

   and removed

   P0Critical issues such as a build break or regressionCritical issues such as a build break or regression

   on Feb 10, 2026
6. reidbaker commented on Feb 10, 2026

   

   reidbaker

   on Feb 10, 2026

   Contributor

   More actions

   I am fine with it being marked flakey but am trying to understand why runtime length matters.

   If we look at the timeline the test takes 40m and fails with a timeout. https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5046/timeline
   If we look at the test step the first to last log line is 6 minutes but the step times out at 30m.

   [2026-02-03 01:31:19.502595] [STDOUT] The Dart VM service is listening on http://127.0.0.1:43417/bo88CpGVYmk=/
   [2026-02-03 01:37:13.226457] [STDOUT] stdout: 00:03 +2: end-to-end test cutout handles rotation
   

   If we look at the file under test

   flutter/dev/integration_tests/display_cutout_rotation/integration_test/display_cutout_test.dart

   Line 16 in 9bda20a

   group('end-to-end test', () {

   there are 3 tests and they all pass.

   So the flake is somewhere in signaling that the test is done.
7. Piinks commented on Feb 10, 2026

   

   Piinks

   on Feb 10, 2026

   Contributor

   More actions

   trying to understand why runtime length matters.

   Oh I checked the runtime based on @jtmcdole's guidance. If a flaky shard is running for 40 minutes, that has more impact on the tree being closed than a shard that runs for 2 minutes. I have just made a habit of checking and noting the runtime when I go through flaky P0s. Sometimes we have so many of them, and they aren't really P0s, so runtime can help signal priority.

   👍React with 👍1Reacted by John "codefu" McDole
8. reidbaker commented on Feb 10, 2026

   

   reidbaker

   on Feb 10, 2026

   Contributor

   More actions

   That makes sense in this case we could shorten the timeout but let the android team investigate first.
9. flutter-zl

   added a commit that references this issue on Feb 10, 2026

   Marks Linux_android_emu android_display_cutout to be flaky (flutter#1…

   ...

   ec29f35
10. fluttergithubbot commented on Feb 18, 2026

    

    fluttergithubbot

    on Feb 18, 2026

    ContributorAuthor

    More actions

    [prod pool] flaky ratio for the past (up to) 100 commits between 2026-02-03 and 2026-02-10 is 4.30%. Flaky number: 4; total number: 93.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5144
    Commit: 907562e
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5144
    https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5122
    https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5100
    https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5063

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android_emu%20android_display_cutout&showBringup=true
11. fluttergithubbot commented on Feb 18, 2026

    

    fluttergithubbot

    on Feb 18, 2026

    ContributorAuthor

    More actions

    [staging pool] flaky ratio for the past (up to) 100 commits between 2026-02-10 and 2026-02-17 is 0.00%. Flaky number: 0; total number: 100.
12. rickhohler

    added a commit that references this issue on Feb 19, 2026

    Marks Linux_android_emu android_display_cutout to be flaky (flutter#1…

    ...

    01005c7
13. 7 remaining items

    Load more

14. fluttergithubbot commented on Mar 10, 2026

    

    fluttergithubbot

    on Mar 10, 2026

    ContributorAuthor

    More actions

    [staging pool] flaky ratio for the past (up to) 100 commits between 2026-03-03 and 2026-03-10 is 0.00%. Flaky number: 0; total number: 100.
15. fluttergithubbot commented on Mar 10, 2026

    

    fluttergithubbot

    on Mar 10, 2026

    ContributorAuthor

    More actions

    [prod pool] flaky ratio for the past (up to) 100 commits between 2026-02-08 and 2026-02-10 is 3.70%. Flaky number: 1; total number: 27.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5144
    Commit: 907562e
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5144

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android_emu%20android_display_cutout&showBringup=true
16. fluttergithubbot commented on Mar 10, 2026

    

    fluttergithubbot

    on Mar 10, 2026

    ContributorAuthor

    More actions

    [staging pool] flaky ratio for the past (up to) 100 commits between 2026-03-03 and 2026-03-10 is 0.00%. Flaky number: 0; total number: 100.
17. jtmcdole commented on Mar 10, 2026

    

    jtmcdole

    on Mar 10, 2026

    Member

    More actions

    The duplicate comments are from the flake bot. It has been in staging for a while and looks to be not-flaky any more.
18. fluttergithubbot commented on Mar 11, 2026

    

    fluttergithubbot

    on Mar 11, 2026

    ContributorAuthor

    More actions

    [prod pool] flaky ratio for the past (up to) 100 commits between 2026-02-09 and 2026-02-10 is 4.35%. Flaky number: 1; total number: 23.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5144
    Commit: 907562e
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android_emu%20android_display_cutout/5144

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android_emu%20android_display_cutout&showBringup=true
19. fluttergithubbot commented on Mar 11, 2026

    

    fluttergithubbot

    on Mar 11, 2026

    ContributorAuthor

    More actions

    [staging pool] flaky ratio for the past (up to) 100 commits between 2026-03-03 and 2026-03-10 is 0.00%. Flaky number: 0; total number: 100.
20. jtmcdole

    added a commit that references this issue on Mar 11, 2026

    chore: deflake Linux_android_emu android_display_cutout

    ...

    This issue will close once commit 5befe20 is merged into the 'master' branch.

    5befe20
21. fluttergithubbot commented on Mar 18, 2026

    

    fluttergithubbot

    on Mar 18, 2026

    ContributorAuthor

    More actions

    [staging pool] flaky ratio for the past (up to) 100 commits between 2026-03-10 and 2026-03-17 is 0.00%. Flaky number: 0; total number: 100.
22. github-merge-queue

    added a commit that references this issue on Mar 23, 2026

    chore: deflake Linux_android_emu android_display_cutout (#183522)

    ...

    This issue will close once commit 0d76183 is merged into the 'master' branch.

    0d76183
23. auto-submit

    closed this as completedin #183522on Mar 23, 2026
24. mboetger

    added 2 commits that reference this issue on Mar 26, 2026

    Marks Linux_android_emu android_display_cutout to be flaky (flutter#1…

    ...

    be87ad1

    chore: deflake Linux_android_emu android_display_cutout (flutter#183522)

    ...

    5f5f4bf
25. github-actions commented on Apr 6, 2026

    

    github-actionsbot

    on Apr 6, 2026 – with GitHub Actions

    More 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.
26. github-actions

    locked as resolved and limited conversation to collaborators on Apr 6, 2026
27. ahmedsameha1

    added a commit that references this issue on Apr 14, 2026

    chore: deflake Linux_android_emu android_display_cutout (flutter#183522)

    ...

    This issue will close once commit 8c88614 is merged into the 'master' branch.

    8c88614