Skia's Swarming bots are hosted in three places:
go/skbl lists all Skia Swarming bots.
Machine name like “skia-gce-NNN”, “skia-ct-gce-NNN”, “skia-i-gce-NNN”, “ct-gce-NNN”, “ct-xxx-builder-NNN” -> GCE
gcloud compute ssh --project <project> default@<machine name>. Choose the zone listed on the VM's detail page (see links above). You may also specify the zone using the
Machine name ends with “a9”, “m3”, “m5” -> Chrome Golo/Labs
Machine name starts with “skia-e-”, “skia-i-” (other than “skia-i-gce-NNN”), “skia-rpi-” -> Chapel Hill lab (aka Skolo)
To log in to Skolo bots, see the Skolo maintenance doc remote access section. See the following for OS specific instructions:
If you need to run code on a specific machine/device to debug an issue, the simplest option is to run tryjobs (after adding debugging output to the relevant code). In some cases you may also need to create or modify tryjobs.
For Googlers: If you need more control (e.g. to run GDB) and need to run directly on a swarming bot then you can use leasing.skia.org.
If that does not work then the current trooper can help you bring the device back to your desk and connect it to GoogleGuest Wifi or the Google Test Network.
If you need to make changes on a Skolo device, please check with an Infra team member. Most can be flashed/imaged back to a clean state, but others can not.
If a permanent change needs to be made on the machine (such as an OS or driver update), please file a bug and assign to jcgregorio for reassignment.
For your convenience, the machine skolo-builder is available for checking out and compiling code within the Skolo. See more info in the Skolo maintenance doc remote access section.
See the Skolo maintenance doc.