Skip to content

Mac_mokey microbenchmarks is 3.09% flaky #189123

Description

@fluttergithubbot

The post-submit test builder Mac_mokey microbenchmarks had a flaky ratio 3.09% 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/Mac_mokey%20microbenchmarks/6827
Commit: 12ed6b4

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20microbenchmarks/6827
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20microbenchmarks/6819
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20microbenchmarks/6814

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

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. added
    P0Critical issues such as a build break or regression
    c: flakeTests that sometimes, but not always, incorrectly pass
    on Jul 8, 2026
  2. jmagman commented on Jul 13, 2026

    @jmagman
    Member

    My guess this is because Mac_mokey is running on the old Intel bots. I'm migrating these to beefier ARM bots here #189377. Hopefully the new ARM variant isn't as flaky.

  3. github-actions commented on Jul 27, 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.

  4. locked as resolved and limited conversation to collaborators on Jul 27, 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 team

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions