Chromium OS‎ > ‎Chromium OS Build‎ > ‎

Chromium OS Remote Trybots

Contents

  1. 1 Introduction
  2. 2 Instructions For Using the Remote Trybot
    1. 2.1 Patch in a Gerrit CL
      1. 2.1.1 Example
    2. 2.2 Patch in a local change
      1. 2.2.1 Example
    3. 2.3 Testing on a release branch
    4. 2.4 Create an official release with a trybot
    5. 2.5 Important flags to consider
      1. 2.5.1 Generating test artifacts for hardware test
      2. 2.5.2 Job launched? Wait for it to finish and then...
  3. 3 Other useful flags
  4. 4 Finding your trybot runs on the waterfall

Introduction

Sorry, but this is only available to Google employees at the moment. Make sure you've joined the chromeos-team group.

Remote trybots allow you to perform a trybot run of multiple configs/boards in parallel on remote servers.  A trybot allows you to emulate a cbuildbot run with a set of your changes. The changes are patched to tip of tree (ToT).

It supports patching of both gerrit CL's and changes you've committed locally but haven't uploaded.

The remote trybot waterfall is located at https://uberchromegw.corp.google.com/i/chromiumos.tryserver.

Instructions For Using the Remote Trybot

Run the following from within your repo source checkout:

  • Run cros tryjob --list to see a list of common configs to run with. Use the --all flag to see all possible configs.

Googlers, the first time you run this, it will initiate the sign-in flow. If you accidentally use your @chromium.org account, you can run cipd auth-logout && cipd auth-login to switch to your @google.com account.

Patch in a Gerrit CL

cros tryjob -g [*]<cl_1> [-g ...] config [config...]

Substitute [config [config...]] with a space-separated list of your desired configs. Prepend a '*' to the CL ID to indicate it's an internal CL. The CL ID can be a Gerrit Change-ID or a change number.

Example

cros tryjob -g 4168 -g *1234 caroline-paladin-tryjob caroline-release-tryjob

This runs a tryjob for the alex-paladin and caroline-release configs in parallel. It patches in two CL's: 1) an external CL using a Gerrit change number 2) an internal CL using a Gerrit change number. In case a CL has several patches associated with it, the latest patch is used.

Patch in a local change

cros tryjob -p <project1>[:<branch1>] [-p ...] config [config..]

Specify the name of the project (not the path, look for projectname in .git/config) and optionally the project branch. If no branch is specified the current branch of the project will be used.

Example

cros tryjob -p chromiumos/chromite -p chromiumos/overlays/chromiumos-overlay:my_branch amd64-generic-pre-cq

This patches in any commits in project chromiumos/chromite's current branch and on branch 'my_branch' in project chromiumos/overlays/chromiumos-overlay.

Testing on a release branch

To test patches for a release branch (i.e., R20, R21) use the --branch (-b) option with -g:

cd <repo_root>/chromiumos/chromite
git checkout cros/master
cros tryjob -b release-R20-2268.B -g 4168 alex-pre-cq

Local patches (-p) to branches are not yet supported.
Non-release branches such as factory, u-boot, etc. are not yet supported.

Create an official release with a trybot

Consult the mini-branch guide.

Important flags to consider

Generating test artifacts for hardware test

If you foresee wanting to run autotests using this image in the lab, you must ensure that it produces test artifacts. Until this bug is fixed this is not always guaranteed to occur, and the simplest way to guarantee it is to use the --hwtest command line flag.

Job launched? Wait for it to finish and then...

Optionally download the archived artifacts that the trybot uploaded by clicking on the link in the result email.

Other useful flags

--remote-description

Attach an optional description to a --remote run to make it easier to identify the results when it finishes.(eg: “testing CL:1234 after fixing NameError”).

Finding your trybot runs on the waterfall

The trybot waterfall is organized by bot category. E.g., for caroline-pre-cq, the category is "pre-cq". For caroline-no-vmtest-pre-cq, the category is "no-vmtest-pre-cq". For pineview-release-group, the category is "release".

When you launch your tryjob, it will print a link showing where to find your run. For example:

$ cros tryjob -g 288223 rambi-no-vmtest-pre-cq caroline-release-tryjob
Verifying patches...
Submitting tryjob...
Tryjob submitted!
Go to https://uberchromegw.corp.google.com/i/chromiumos.tryserver/waterfall?committer=davidjames@google.com&builder=no-vmtest-pre-cq&builder=release to view the status of your job.

You can construct the link by replacing the committer and builder to see the status.

If you want to double check the exact category name of any bot, you can look it up either by launching a tryjob with it (see above), or by looking in chromite/cbuildbot/config_dump.json (the template is listed as "_template") under the bot name.

Comments