Ravi Mistry 75a1377e54 Add section for how to connect to Skia swarming bots

No-Try: true
Docs-Preview: https://skia.org/?cl=67849
Bug: skia:7098
Change-Id: Ib603bdd2117aab6f626cd68e26529d277a0f1508
Reviewed-on: https://skia-review.googlesource.com/67849
Commit-Queue: Ravi Mistry <rmistry@google.com>
Reviewed-by: Kevin Lubick <kjlubick@google.com>
Reviewed-by: Ben Wagner <benjaminwagner@google.com>

2017-11-07 01:51:32 +00:00

4.3 KiB

Raw Blame History

Skia Swarming Bots

Overview

Skia's Swarming bots are hosted in three places:

Google Compute Engine. This is the preferred location for bots which don't need to run on physical hardware, ie. anything that doesn't require a GPU or a specific hardware configuration. Most of our compile bots live here, along with some non-GPU test bots on Linux and Windows. We get surprisingly stable performance numbers from GCE, despite very few guarantees about the physical hardware.
Chrome Golo. This is the preferred location for bots which require specific hardware or OS configurations that are not supported by GCE. We have several Mac, Linux, and Windows bots in the Golo.
The Skolo (local Skia lab in Chapel Hill). Anything we can't get in GCE or the Golo lives here. This includes a wider variety of GPUs and all Android, ChromeOS, iOS, and other devices.

go/skbl lists all Skia Swarming bots.

Connecting to Swarming Bots

Machine name like “skia-gce-NNN”, “skia-i-gce-NNN”, “ct-gce-NNN”, “skia-ct-gce-NNN”, “ct-xxx-builder-NNN” -> GCE
- To log in to a Linux bot in GCE, use gcloud compute ssh default@<machine name>. Choose the zone listed for the GCE VM (or specify it using the --zone command-line flag).
- To log in to a Windows bot in GCE, use Chrome RDP Extension with the IP address of the GCE VM. The username is chrome-bot and the password can be found on Valentine as "chrome-bot (Win GCE)".
Machine name ends with “a9”, “m3”, "m5" -> Chrome Golo/Labs
- To log in to Golo bots, see go/swarming-ssh.
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:

Debugging

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 run to 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.

Maintenance Tasks

See the Skolo maintenance doc.

4.3 KiB Raw Blame History