-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Comments
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. |
[prod pool] current flaky ratio for the past (up to) 100 commits is 1.04%. Flaky number: 1; total number: 96. Recent test runs: |
[staging pool] current flaky ratio for the past (up to) 100 commits is 0.00%. Flaky number: 0; total number: 69. |
Closing due to flake rate below the threshold. |
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 |
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).
The text was updated successfully, but these errors were encountered: