Mac_mokey run_debug_test_android is 3.03% flaky
- Dominant language
- Dart
- Stars
- 179k
- Forks
- 31.1k
- PR merge metrics
- PR metrics pending
Description
The post-submit test builder `Mac_mokey run_debug_test_android` had a flaky ratio 3.03% 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%20run_debug_test_android/7800
Commit: https://github.com/flutter/flutter/commit/92a5797d83bd958001a0680b16fa11f076961b11
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/7800
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/7798
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/7746
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_mokey%20run_debug_test_android
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).
Contributor guide
Research direction
Start with docs/infra/Reducing-Test-Flakiness.md and inspect the linked Mac_mokey run_debug_test_android flaky builds and recent test runs. Identify the source of the flakiness, validate the fix using the referenced internal dashboard, and enable the test again once the flakiness is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart, flutter
- Domain
- ci-cd, mobile, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100