This page describes the Gerrit Commit Queue for Chromium OS (also known by the code name "Paladin")
The goal of the Commit Queue is to vet changes (build and test them on multiple platforms) and push them on behalf of developers. It is responsible for not only committing changes, but also doing the Portage voodoo (uprevving ebuilds) necessary for other developers to see each others changes.
We first launch a trybot to sanity check your change. This trybot will compile your change and run unit tests on 3 major platforms. This check only includes your change and related changes, and takes about 20 minutes.
The commit queue runs approximately once an hour, and picks up all changes that have been fully verified by trybots. It builds a full image (on >15 platforms) and runs tests on both virtual machines and real hardware. Each commit queue run takes approximately an hour.
The Commit Queue only runs when the tree is open, and only picks up changes that have been approved, verified and marked ready. The commit queue also only picks up changes if all of their dependencies have been similarly approved, verified, and marked ready (see the "How do I specify the dependencies of a change?" section below).
Yes. This means that the Commit Queue will not try a change that depends on another until both it and the change it depends on are marked as ready for commit.
If you commit a stack of CLs to a branch locally, and upload them all together, Gerrit will already know about your dependencies and the commit queue will honor these dependencies.
If you want to specify a dependency on other CLs, you can specify a dependency on any CL in Gerrit by using CQ-DEPEND. Here's how it works:
Here's an example:
If you have internal commit rights, yes you can. You can launch a trybot run using the following command:
If you pre-verify your change using the "pre-cq-group" trybot, the commit queue will not launch a trybot run again.
For more details on remote trybots, see the remote trybot documentation.
All projects under chromiumos/* and chromeos/* in gerrit and gerrit-int respectively are managed by the commit queue.
In order to see what the Commit Queue is doing, you can view its current work on the internal and external waterfalls.
There are three places where the commit queue can fail to commit your change.
If you need more information about a build failure, you can look at the commit-queue builders on the internal and external waterfalls and find the build run which has your CL in the CommitQueueSync stage. These are the same logs other builders would have so delve accordingly. The Commit Queue also sends a snippet of the build log and a link to help you debug the issue.
Please do not bypass the commit queue unless it is necessary. That said, to bypass the commit queue, hit the submit patch button and select "Yes, I'm a chump".
If the Commit Queue finds that there are no changes that have been verified by trybots, the commit queue will start picking up unverified changes. This should only happen either at off-hours (when few developers are submitting changes) or when the trybot waterfall is having issues.
If the Commit Queue is down or consistently broken, please close the tree and contact a Build Sheriff or trooper immediately (chrome-troopers [at] google.com).
Contact: davidjames, sosa, or rcui @ chromium