-
Notifications
You must be signed in to change notification settings - Fork 26.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate devicelab from A02s's and MotoG4's to Mokey's #148085
Comments
Marking |
@zanderso, Please let me know when your teams ready to switch the phone devices from A02s and MotoG4s to new Mokey's phone devices. And also, which phone model to switch out first, A02s or MotoG4s? |
Sounds like we have 20 devices so far. I think the sticky note on my desk claims we'll need 3X devices, so I'll flash the rest next week. |
@zanderso the box next to your desk is full of all of the flashed mokey devices that are ready for the devicelab |
@jonahwilliams Just want to make correction. There are 18 Mokey devices in the Devicelab, one device won't charge and other device different model was missed up in the pile. |
We don't currently have much running on the a02s's. After #148563 lands, they can all be swapped out for mokeys. |
bringup: true
.bringup: true
from the tests on MokeyYusuf wrote up this doc to describe where we'd like to get to for how devices are allocated in the lab across pools and devices: go/flutter-devicelab-testbed-matrix
Current allocation between try, staging, and prod pools can be queried in https://chromium-swarm.appspot.com/botlist.
We can move hosts between staging and prod by editing:
https://chrome-internal.googlesource.com/infradata/config/+/refs/heads/main/configs/chromium-swarm/starlark/bots/flutter.star. There are extra steps that I don't know to check in extra files that are generated from the .star files.
Kent: nguyenkent@
The text was updated successfully, but these errors were encountered: