pw_presubmit: Add more ResultDB Metadata

Consider tests executed by different builders, or in different steps, as
different "test variants" (go/resultdb-concepts#test-variant).

Create a subinvocation for each step, to group together tests executed
in the same step.

Bug: 247857184
Change-Id: I4adae5341d3c27cdb8a0ae1f31430ea5cf4b35e0
Commit-Queue: Auto-Submit <>
Reviewed-by: Rob Mohr <>
Pigweed-Auto-Submit: Ted Pudlik <>
7 files changed
tree: ed63dc6b94a4a32ef2dc51783055e84ce5c542ba
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. .gitignore
  6. .style.yapf
  8. cipd.ensure
  10. OWNERS
  12. pyproject.toml

Pigweed Recipes

This repository contains recipes for Pigweed.

A recipe is a Python script that runs a series of commands, using the recipe engine framework from the LUCI project. We use recipes to automatically check out, build, and test Pigweed and downstream projects using Pigweed in continuous integration jobs. The commands the recipes use are very similar to the ones you would use as a developer to check out, build, and test Pigweed in your local environment.

See go/pigweed-recipe-docs for complete documentation and a guide for getting started with writing recipes.

Getting the Code

The recommended way to get the source code is with git.

git clone

In most cases you will need a Chromium depot_tools checkout in your PATH as well.

git clone ~/depot_tools
echo 'export PATH="$PATH:$HOME/depot_tools"' >> ~/.bashrc

Running Tests

./ runs three different sets of tests:

  • Recipe expectation tests (./ test train)
  • Formatting (./black --diff --check .)
  • Dependencies (.recipe_deps/fuchsia/scripts/ --check)

The formatting check will tell you what‘s wrong but not fix it. For that you need to run ./black .. Similarly, the dependencies check will tell you what’s wrong but you'll need to edit the files to fix issues.

If not using ./ you'll need to run ./scripts/ before ./black is present.