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
Move devicelab benchmark builders from staging to prod #105468
These builders were moved to staging due to their high flaky rate. As of today, linux/android ones have been pretty stable without a single flak in recent 500 runs, and we should move them to prod. This can help monitor the tests more closely (avoiding issues like #105464).
Linux/android ones are ready to move, whereas the mac/ios ones are still flaky and we can monitor and move later if flake is clear.
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
keyonghan commentedon Jun 6, 2022
/cc @ricardoamador could you please help with this one?
ricardoamador commentedon Jun 6, 2022
Yes sir. I'll take a look.
keyonghan commentedon Jun 6, 2022
Action items:
bringup: truefirstkeyonghan commentedon Jun 7, 2022
/cc @zanderso These linux builders have been enabled in flutter dashboard, and will be removed from devicelab_benchmark console via https://flutter-review.googlesource.com/c/infra/+/31020.
zanderso commentedon Jun 8, 2022
Thanks!
ricardoamador commentedon Jun 8, 2022
I have moved flutter-linux-14 and flutter-linux-15 from staging to prod.
ricardoamador commentedon Jun 16, 2022
This has been completed.
ricardoamador commentedon Jun 16, 2022
Reopening to track the move of the IOS bots.
keyonghan commentedon Aug 22, 2022
F.Y.I: #110037. This should be ready to go without any blockers. /cc @ricardoamador
ricardoamador commentedon Aug 22, 2022
@keyonghan on it.
ricardoamador commentedon Aug 23, 2022
IOS Benchmark tests have been moved to prod.
zanderso commentedon Aug 29, 2022
Thanks!
github-actions commentedon Sep 12, 2022
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.