The Chromium Projects

Search this site

Except as otherwise noted, the content of this page is licensed under a Creative Commons Attribution 2.5 license, and examples are licensed under the BSD License.

Bypassing tests on a per-project basis

Some repositories (e.g. firmware repositories) contain code that is very unlikely to break hardware tests. When these tests fail, CLs in these repositories would normally be rejected unfairly. To prevent this unfair treatment, it is now possible to configure what tests should be bypassed in a COMMIT-QUEUE.ini file.

COMMIT-QUEUE.ini files should be created in the root directory of your repository. Here is an example COMMIT-QUEUE.ini file for the coreboot repository, which lives in src/third_party/coreboot/COMMIT-QUEUE.ini:

# Copyright (c) 2013 The Chromium OS Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.

# Per-project Commit Queue settings.
# Documentation: http://goo.gl/4rZhAx

[GENERAL]

# Stages to ignore in the commit queue. If these steps break, your CL will be
# submitted anyway. Use with caution.
ignored-stages: HWTest VMTest

In the case where the HWTest or VMTest steps fail, cbuildbot will ignore the failure and submit the CLs anyway.

What stages can be ignored?

Currently, the following stages can be ignored:
  • UnitTest: Run unit tests for all packages.
  • VMTest: Run the ChromeOS smoke suite in a virtual machine
  • HWTest: Run the ChromeOS BVT in a virtual machine
  • UploadPrebuilts: Upload prebuilt binaries for all changes.
  • Archive: Miscellaneous steps for building and archiving artifacts, including building factory images, firmware tarballs, and recovery images.

Comments