Skip to content

Linux_pixel_7pro drive_perf_debug_warning is 2.06% flaky #174111

Closed
#181277
Closed
Linux_pixel_7pro drive_perf_debug_warning is 2.06% flaky#174111
#181277
Assignees
jtmcdole
Labels
P1High-priority issues at the top of the work listc: flakeTests that sometimes, but not always, incorrectly passteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

Description

@fluttergithubbot
fluttergithubbot
opened on Aug 20, 2025

The post-submit test builder Linux_pixel_7pro drive_perf_debug_warning had a flaky ratio 2.06% 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_pixel_7pro%20drive_perf_debug_warning/8940
Commit: 880572e

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro%20drive_perf_debug_warning/8940
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro%20drive_perf_debug_warning/8922

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_pixel_7pro%20drive_perf_debug_warning

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

  1. fluttergithubbot
    assigned
    jtmcdole
    on Aug 20, 2025
  2. fluttergithubbot
    added
    P0Critical issues such as a build break or regression
    c: flakeTests that sometimes, but not always, incorrectly pass
    team-engineOwned by Engine team
    on Aug 20, 2025

  3. chinmaygarde commented on Aug 25, 2025

    @chinmaygarde
    chinmaygarde
    on Aug 25, 2025
    Contributor

    The test could not connect to an Android device.

  4. chinmaygarde
    added
    triaged-engineTriaged by Engine team
    on Aug 25, 2025
  5. github-merge-queue
    added a commit that references this issue on Aug 28, 2025

    Marks Linux_pixel_7pro drive_perf_debug_warning to be flaky (#174112)

    a16a112

  6. Piinks commented on Sep 2, 2025

    @Piinks
    Piinks
    on Sep 2, 2025
    Contributor

    @jtmcdole (from triage meeting)

  7. fluttergithubbot commented on Sep 3, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 3, 2025
    ContributorAuthor

    [prod pool] flaky ratio for the past (up to) 100 commits between 2025-08-22 and 2025-08-28 is 0.00%. Flaky number: 0; total number: 95.

  8. fluttergithubbot commented on Sep 3, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 3, 2025
    ContributorAuthor

    [staging pool] flaky ratio for the past (up to) 100 commits between 2025-08-28 and 2025-09-02 is 0.00%. Flaky number: 0; total number: 57.

  9. fluttergithubbot commented on Sep 10, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 10, 2025
    ContributorAuthor

    [prod pool] flaky ratio for the past (up to) 100 commits between 2025-08-22 and 2025-08-28 is 0.00%. Flaky number: 0; total number: 94.

  10. fluttergithubbot commented on Sep 10, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 10, 2025
    ContributorAuthor

    [staging pool] flaky ratio for the past (up to) 100 commits between 2025-09-02 and 2025-09-09 is 4.00%. Flaky number: 4; total number: 100.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/125
    Commit: 251f4a8
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/96
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/84
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/125
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/119

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_pixel_7pro%20drive_perf_debug_warning&showBringup=true

  11. Piinks commented on Sep 15, 2025

    @Piinks
    Piinks
    on Sep 15, 2025
    Contributor

    @jtmcdole is this still a P0?

  12. fluttergithubbot commented on Sep 17, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 17, 2025
    ContributorAuthor

    [prod pool] flaky ratio for the past (up to) 100 commits between 2025-08-22 and 2025-08-28 is 0.00%. Flaky number: 0; total number: 90.

  13. fluttergithubbot commented on Sep 17, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 17, 2025
    ContributorAuthor

    [staging pool] flaky ratio for the past (up to) 100 commits between 2025-09-07 and 2025-09-16 is 2.00%. Flaky number: 2; total number: 100.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/231
    Commit: 1586c0c
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/231
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/221

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_pixel_7pro%20drive_perf_debug_warning&showBringup=true

  14. 3 remaining items

  15. Piinks
    added
    P1High-priority issues at the top of the work list
    and removed
    P0Critical issues such as a build break or regression
    on Sep 22, 2025

  16. fluttergithubbot commented on Sep 24, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 24, 2025
    ContributorAuthor

    [prod pool] flaky ratio for the past (up to) 100 commits between 2025-08-25 and 2025-08-28 is 0.00%. Flaky number: 0; total number: 82.

  17. fluttergithubbot commented on Sep 24, 2025

    @fluttergithubbot
    fluttergithubbot
    on Sep 24, 2025
    ContributorAuthor

    [staging pool] flaky ratio for the past (up to) 100 commits between 2025-09-16 and 2025-09-23 is 1.00%. Flaky number: 1; total number: 100.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/281
    Commit: 3f2611e
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/281

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_pixel_7pro%20drive_perf_debug_warning&showBringup=true

  18. Jaineel-Mamtora
    added a commit that references this issue on Sep 24, 2025

    Marks Linux_pixel_7pro drive_perf_debug_warning to be flaky (flutter#…

    5a28f53

  19. fluttergithubbot commented on Oct 1, 2025

    @fluttergithubbot
    fluttergithubbot
    on Oct 1, 2025
    ContributorAuthor

    [staging pool] flaky ratio for the past (up to) 100 commits between 2025-09-24 and 2025-09-30 is 0.00%. Flaky number: 0; total number: 100.

  20. fluttergithubbot commented on Oct 8, 2025

    @fluttergithubbot
    fluttergithubbot
    on Oct 8, 2025
    ContributorAuthor

    [staging pool] flaky ratio for the past (up to) 100 commits between 2025-09-30 and 2025-10-07 is 3.00%. Flaky number: 3; total number: 100.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/574
    Commit: fafb7a2
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/574
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/565
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/536

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_pixel_7pro%20drive_perf_debug_warning&showBringup=true

  21. fluttergithubbot commented on Oct 15, 2025

    @fluttergithubbot
    fluttergithubbot
    on Oct 15, 2025
    ContributorAuthor

    [staging pool] flaky ratio for the past (up to) 100 commits between 2025-10-06 and 2025-10-14 is 3.00%. Flaky number: 3; total number: 100.
    One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/625
    Commit: cd189a1
    Flaky builds:
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/625
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/619
    https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20drive_perf_debug_warning/574

    Recent test runs:
    https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_pixel_7pro%20drive_perf_debug_warning&showBringup=true

  22. jtmcdole commented on Oct 15, 2025

    @jtmcdole
    jtmcdole
    on Oct 15, 2025
    Member

    Task failed: DeviceException: No Android devices detected

  23. jtmcdole
    closed this as completedon Oct 15, 2025

  24. github-actions commented on Oct 29, 2025

    @github-actions
    github-actionsbot
    on Oct 29, 2025 – with 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.

  25. github-actions
    locked as resolved and limited conversation to collaborators on Oct 29, 2025
  26. github-merge-queue
    added a commit that references this issue on Jan 21, 2026

    Marks drive_perf_debug_warning to be unflaky (#181277)

    82eac0a
  27. flutter-zl
    added a commit that references this issue on Feb 10, 2026

    Marks drive_perf_debug_warning to be unflaky (flutter#181277)

    f9d1b7e
  28. Nakiha
    added a commit that references this issue on Sep 28, 2026

    Marks drive_perf_debug_warning to be unflaky (#181277)

    b8e5217
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1High-priority issues at the top of the work listc: 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