Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mac_android microbenchmarks is 2.06% flaky #118692

Closed
fluttergithubbot opened this issue Jan 18, 2023 · 5 comments
Closed

Mac_android microbenchmarks is 2.06% flaky #118692

fluttergithubbot opened this issue Jan 18, 2023 · 5 comments
Assignees
Labels
c: flake Tests that sometimes, but not always, incorrectly pass P0 Critical issues such as a build break or regression platform-android Android applications specifically

Comments

@fluttergithubbot
Copy link
Contributor

The post-submit test builder Mac_android microbenchmarks 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/Mac_android%20microbenchmarks/8611
Commit: 13a8dce

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android%20microbenchmarks/8611
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android%20microbenchmarks/8579

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

Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).

@fluttergithubbot fluttergithubbot added engine flutter/engine repository. See also e: labels. P1 c: flake Tests that sometimes, but not always, incorrectly pass labels Jan 18, 2023
@zanderso
Copy link
Member

In 8611, it looks like one of the microbenchmarks failed to generate the expected json result, but the logs don't indicate what went wrong.

In 8579, the test timed-out after 30 minutes.

Routing to the Android team for further investigation.

@zanderso zanderso removed their assignment Jan 18, 2023
@zanderso zanderso added platform-android Android applications specifically and removed engine flutter/engine repository. See also e: labels. labels Jan 18, 2023
@fluttergithubbot
Copy link
Contributor Author

[prod pool] current flaky ratio for the past (up to) 100 commits is 1.04%. Flaky number: 1; total number: 96.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android%20microbenchmarks/8611
Commit: 13a8dce
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android%20microbenchmarks/8611

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

@fluttergithubbot
Copy link
Contributor Author

[staging pool] current flaky ratio for the past (up to) 100 commits is 0.00%. Flaky number: 0; total number: 69.

@zanderso
Copy link
Member

Closing due to flake rate below the threshold.

@github-actions
Copy link

github-actions bot commented Mar 4, 2023

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 4, 2023
@flutter-triage-bot flutter-triage-bot bot added P0 Critical issues such as a build break or regression and removed P1 labels Jun 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
c: flake Tests that sometimes, but not always, incorrectly pass P0 Critical issues such as a build break or regression platform-android Android applications specifically
Projects
None yet
Development

No branches or pull requests

3 participants