Roll recipe dependencies (nontrivial).

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

Please review the expectation changes, and LGTM+CQ.

  c417174 (
      Revert "Roll recipe dependencies (trivial)."
  f14e223 (
      [macos_sdk] Roll mac_toolcahin to 3e597065cb23c1fe03aeb2ebd792d...
  9305e13 (
      [firebase_docs] Use infra's python binary

  b60bb0d (
      Revert "[] Unset PYTHONPATH in case users have confli...

Please check the following references for more information:
- autoroller,
- rollback,
- cross-repo dependencies,

Use to file a bug.,

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: I0bcf9e51089a4bdf4e66f6460f512a226c6f8c25
Presubmit-Verified: CQ Bot Account <>
Reviewed-by: Rob Mohr <>
Commit-Queue: Rob Mohr <>
3 files changed
tree: ced3e5e4ba28e36bf0f43cd50b52526a5f61c38c
  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.