Repository navigation
Mac_android microbenchmarks is 2.06% flaky #118692
Description
Activity
- addedengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.c: flakeTests that sometimes, but not always, incorrectly passTests that sometimes, but not always, incorrectly pass
on Jan 18, 2023 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.
- addedplatform-androidAndroid applications specificallyAndroid applications specificallyand removedengineflutter/engine related. See also e: labels.flutter/engine related. See also e: labels.
on Jan 18, 2023 fluttergithubbot commented
on Jan 25, 2023 ContributorAuthorMore actions[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/8611Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_android%20microbenchmarksfluttergithubbot commented
on Jan 25, 2023 ContributorAuthorMore actions[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
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Mar 4, 2023 - addedP0Critical issues such as a build break or regressionCritical issues such as a build break or regressionand removed
on Jun 28, 2023
The post-submit test builder
Mac_android microbenchmarkshad 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).