Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (fuchsia, recipe_engine) into this repository.

The build that created this CL was

  c03c9b3 (
      [roll] Update tools to latest
  c268846 (
      [testing_requests] Add nsjail-root to testrunner command.
  00ac664 (
      [roll] Update tools to latest
  a49b7e0 (
      [autocorrelator] Use api.runtime.in_global_shutdown
  6e7a43b (
      [roll] Update tools to latest
  8dbe627 (
      Don't run steps during build shutdown
  6c1ba2e (
      [roll] Update tools to latest
  adf999d (
      Add branch to checkout step and submodule update tool input

  7ef38ce (
      [] Don't silence `git fetch` stderr

More info is at Use to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: Ib0dc1153e0ab0b2dab42b8a9e20fe8b1f484793e
Bot-Commit: Recipe Deps Roller <>
Commit-Queue: Recipe Deps Roller <>
2 files changed
tree: 7ea78e98edfdccce56133858190e6157bb286f51
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. .gitignore
  6. .style.yapf
  9. cipd.ensure
  11. 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.