The trybots let committers try uncommitted patches on multiple platforms in an automated way.
git cl tryor the “Choose Trybots” UI in gerrit.
Upload your change to gerrit via
git cl upload
Run the default set of trybots by starting a CQ dry run, either by setting CQ+1 on gerrit or by running
git cl try with no arguments.
Run trybots of your choice by providing arguments to
git cl try:
-B/--bucket. For chromium tryjobs, this should always be
-b/--bot. This can be specified more than once.
Launching a CQ dry run:
$ git cl try
Launching a particular trybot:
$ git cl try -B luci.chromium.try -b linux-rel
Launching multiple trybots:
$ git cl try -B luci.chromium.try \ -b android-binary-size \ -b ios-simulator-full-configs \ -b linux-blink-rel \ -b win7-blink-rel # etc
It is also possible to run a Chromium try job with a pending CL in a separate repository that is synced via DEPS. Normally DEPS files specify the SHA1 revision hash of the dependency. But commits that are part of pending CLs are not part of the default refspec fetched when gclient checks out the dependency. Instead, you can specify a symbolic reference to your change, like
refs/changes/12/2277112/3. To determine the ref to use, click the “Download” button on the dependency CL in Gerrit, which will show it as part of several git commands. Then edit the DEPS file in Chromium.
If, for example, you wanted to test a pending V8 CL in Chromium, you would edit the DEPS line, which may look like this:
And change it to:
When you run the try job, gclient will sync in your pending CL. Note that if your pending CL is based on a revision that is either older or newer than the revision specified in DEPS, the tryjob may fail. You can rebase your CL to be on top of the same revision specified in the DEPS file to avoid this.