Repository navigation
Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark is 3.00% flaky #158241
Description
The post-submit test builder Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark had a flaky ratio 3.00% 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_arm64_ios%20hot_mode_dev_cycle_ios__benchmark/1520
Commit: 2da2332
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64_ios%20hot_mode_dev_cycle_ios__benchmark/1520
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64_ios%20hot_mode_dev_cycle_ios__benchmark/1515
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64_ios%20hot_mode_dev_cycle_ios__benchmark/1483
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_arm64_ios%20hot_mode_dev_cycle_ios__benchmark
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
Marks Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark to be flaky (#1…
fluttergithubbot commentedon Nov 13, 2024
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-11-05 and 2024-11-12 is 0.00%. Flaky number: 0; total number: 94.
zanderso commentedon Nov 13, 2024
@LouiseHsu the arm64 macs in the devicelab staging pool are having some problems: #158740.
Since the flake rate is low, I'd suggest moving this test back to the prod pool. That is, reverting #158242.
Reverts "Marks Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark to be …
LouiseHsu commentedon Nov 13, 2024
reverted!
Piinks commentedon Nov 19, 2024
(Triage): Thanks @LouiseHsu, with that revert landed, does that mean this issue is resolved?
LouiseHsu commentedon Nov 19, 2024
@Piinks mmm, I only see one flake since the revert landed, which is lower than the threshold. I'm gonna close this. 👀
github-actions commentedon Dec 4, 2024
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.