You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mac_benchmark complex_layout_scroll_perf_macos__timeline_summary is 2.15% flaky #158251
The post-submit test builder Mac_benchmark complex_layout_scroll_perf_macos__timeline_summary had a flaky ratio 2.15% for the past (up to) 100 commits, which is above our 2.00% 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 -v and a minimal reproduction of the issue.
Activity
Marks Mac_benchmark complex_layout_scroll_perf_macos__timeline_summar…
chunhtai commentedon Nov 12, 2024
downgrade to p2 since it is already marked as flaky
fluttergithubbot commentedon Nov 20, 2024
[prod pool] flaky ratio for the past (up to) 100 commits between 2024-11-03 and 2024-11-09 is 2.27%. Flaky number: 2; total number: 88.
One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_benchmark%20complex_layout_scroll_perf_macos__timeline_summary/10301
Commit: 66e8f53
Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_benchmark%20complex_layout_scroll_perf_macos__timeline_summary/10301
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_benchmark%20complex_layout_scroll_perf_macos__timeline_summary/10291
Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_benchmark%20complex_layout_scroll_perf_macos__timeline_summary
fluttergithubbot commentedon Nov 20, 2024
[staging pool] flaky ratio for the past (up to) 100 commits between 2024-11-12 and 2024-11-19 is 0.00%. Flaky number: 0; total number: 100.
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.