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

  6b6c067 (
      [roll] Update tools to latest
  9ba8f11 (
      [artifacts] Don't infra-fail if build was cancelled
  0b8f4f5 (
      [create_branch] Allow empty commit post-config gen
  20cf3d4 (
      Change snapshot_path to include all ensure and version files
  60e831d (
      [roll] Update tools to latest
  e73ef8d (
      [roll] Update tools to latest
  e8554cf (
      [roll] Update tools to latest
  20ddf0f (
      [roll] Update tools to latest
  afa034d (
      [roll] Update tools to latest
  f9454f8 (
      Remove snapshot_file
  11a4785 (
      [roll] Update tools to latest
  6d2bd74 (
      [git] Add helper to cherry-pick a CL
  2ea2f23 (
      [checkout] Slightly generalize _apply_patch()
  d8281dc (
      [roll] Update tools to latest

  312823d (
      Convert git stdin/stdout to and from bytes.
  a476355 (
      Roll CAS Client from a169f70aa54e to 09f8b3edbbf1

More info is at Use to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: I861bfcbf0fdf3b7fe954a1df26f6361bff112bcc
Bot-Commit: Recipe Deps Roller <>
Commit-Queue: Recipe Deps Roller <>
1 file changed
tree: c469ce9ae0fcdd1583aeb7e3d226460ed4ca3634
  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.