1Skia Swarming Bots 2================== 3 4Overview 5-------- 6 7Skia's Swarming bots are hosted in three places: 8 9* Google Compute Engine. This is the preferred location for bots which don't need to run on physical 10 hardware, ie. anything that doesn't require a GPU or a specific hardware configuration. Most of 11 our compile bots live here, along with some non-GPU test bots on Linux and Windows. We get 12 surprisingly stable performance numbers from GCE, despite very few guarantees about the physical 13 hardware. 14* Chrome Golo. This is the preferred location for bots which require specific hardware or OS 15 configurations that are not supported by GCE. We have several Mac, Linux, and Windows bots in the 16 Golo. 17* The Skolo (local Skia lab in Chapel Hill). Anything we can't get in GCE or the Golo lives 18 here. This includes a wider variety of GPUs and all Android, ChromeOS, iOS, and other devices. 19 20[go/skbl](https://goto.google.com/skbl) lists all Skia Swarming bots. 21 22 23<a name="connecting-to-swarming-bots"></a> 24Connecting to Swarming Bots 25--------------------------- 26 27- Machine name like “skia-gce-NNN”, “skia-ct-gce-NNN”, “skia-i-gce-NNN”, “ct-gce-NNN”, “ct-xxx-builder-NNN” -> GCE 28 * First determine the project for the bot: 29 + skia-gce-NNN, skia-ct-gce-NNN: [skia-swarming-bots](https://console.cloud.google.com/compute/instances?project=skia-swarming-bots) 30 + skia-i-gce-NNN: [google.com:skia-buildbots](https://console.cloud.google.com/compute/instances?project=google.com:skia-buildbots) 31 + ct-gce-NNN, ct-xxx-builder-NNN: [ct-swarming-bots](https://console.cloud.google.com/compute/instances?project=ct-swarming-bots) 32 * To log in to a Linux bot in GCE, use `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 `--zone` command-line flag. 33 * To log in to a Windows bot in GCE, on the VM's detail page, first click the "Set Windows password" button, then click the "RDP" button. (If it hasn't been installed, you will be instructed to install the Chrome RDP Extension for GCP.) 34 35- Machine name ends with “a9”, “m3”, "m5" -> Chrome Golo/Labs 36 * To log in to Golo bots, see [go/chrome-infra-build-access](https://goto.google.com/chrome-infra-build-access). 37 38- Machine name starts with “skia-e-”, “skia-i-” (other than “skia-i-gce-NNN”), “skia-rpi-” -> Chapel Hill lab (aka Skolo)<br/> 39 To log in to Skolo bots, see the [Skolo maintenance doc][remote access] remote access section. See the following for OS specific instructions:<br/> 40 * [Remotely debug an Android device in Skolo][remotely debug android] 41 * [VNC to Skolo Windows bots][vnc to skolo windows] 42 * [ChromeOS Debugging][chromeos debugging] 43 44 45Debugging 46--------- 47 48If you need to run code on a specific machine/device to debug an issue, the simplest option is to 49run tryjobs (after adding debugging output to the relevant code). In some cases you may also need to 50[create or modify tryjobs](automated_testing#adding-new-jobs). 51 52For Googlers: If you need more control (e.g. to run GDB) and need run to directly on a swarming bot then you can use [leasing.skia.org](https://leasing.skia.org).<br/> 53If that does not work then the [current trooper][current trooper] can help you bring the device back to your desk and connect 54it to GoogleGuest Wifi or the [Google Test Network](http://go/gtn-criteria). 55 56If you need to make changes on a Skolo device, please check with an Infra team member. Most can be 57flashed/imaged back to a clean state, but others can not. 58 59If a permanent change needs to be made on the machine (such as an OS or driver update), please [file 60a bug][infra bug] and assign to jcgregorio for reassignment. 61 62[current trooper]: http://skia-tree-status.appspot.com/trooper 63[remote access]: 64 https://docs.google.com/document/d/1zTR1YtrIFBo-fRWgbUgvJNVJ-s_4_sNjTrHIoX2vulo/edit#heading=h.2nq3yd1axg0n 65[infra bug]: https://bugs.chromium.org/p/skia/issues/entry?template=Infrastructure+Bug 66[remotely debug android]: https://docs.google.com/document/d/1nxn7TobfaLNNfhSTiwstOnjV0jCxYUI1uwW0T_V7BYg/ 67[vnc to skolo windows]: 68 https://docs.google.com/document/d/1zTR1YtrIFBo-fRWgbUgvJNVJ-s_4_sNjTrHIoX2vulo/edit#heading=h.7cqd856ft0s 69[chromeos debugging]: 70 https://docs.google.com/document/d/1yJ2LLfLzV6pXKjiameid1LHEz1mj71Ob4wySIYxlBdw/edit#heading=h.9arg79l59xrf 71 72Maintenance Tasks 73----------------- 74 75See the [Skolo maintenance doc][skolo maintenance]. 76 77[skolo maintenance]: 78 https://docs.google.com/document/d/1zTR1YtrIFBo-fRWgbUgvJNVJ-s_4_sNjTrHIoX2vulo/edit 79