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
https://ci.chromium.org/b/8827799882799394881

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/ec66eff6a97cd146f8e6b112b1a7d5719b55e5b2~..a5085bcd96cdd4ba11965cf09b3f3f6cb1c83fd7
  ec66eff (olivernewman@google.com)
      [sdk] Pass SDK ID to subbuild via sdk_id property
  2e427a4 (yupingz@google.com)
      [submodule_update] Add jiri snapshot cipd files to builder
  2390818 (atyfto@google.com)
      [snap_branch] Don't short-circuit petal snap for fast-forwards
  8c2c0f1 (yupingz@google.com)
      [submodule_update] Fix jiri snapshot cipd files step.
  57a1571 (olivernewman@google.com)
      [build] Copy assembly inputs instead of symlinking
  ff42bad (olivernewman@google.com)
      Stop using api.python.*_step methods
  da7ca9f (yuanzhi@google.com)
      [femu] Allow recipe_tools_roller to pick up manifest from subdir.
  a5085bc (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/8014513b5deebe215d620fdcac9abd928556d8a8~..ab96fada0d67fab3a7e4e7801d63db7e6982a23c
  8014513 (olivernewman@google.com)
      [warnings] Fix python result_step warnings
  ab96fad (iannucci@chromium.org)
      Add `empty` to step module.

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug.

R=tpudlik@google.com

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: I0f0a537c20d55abf4bfaf66b09695fcd1bf55a6f
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/74420
Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
1 file changed
tree: 9baa81b3a51ea5efa525c415e9db457e2d33b233
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. .gitignore
  6. .style.yapf
  7. cipd.ensure
  8. OWNERS
  9. presubmit.sh
  10. pyproject.toml
  11. README.md
  12. recipes.py
README.md

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 https://pigweed.googlesource.com/infra/recipes

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

git clone https://chromium.googlesource.com/chromium/tools/depot_tools ~/depot_tools
echo 'export PATH="$PATH:$HOME/depot_tools"' >> ~/.bashrc

Running Tests

./presubmit.sh runs three different sets of tests:

  • Recipe expectation tests (./recipes.py test train)
  • Formatting (./black --diff --check .)
  • Dependencies (.recipe_deps/fuchsia/scripts/cleanup_deps.py --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 ./presubmit.sh you'll need to run ./scripts/ensure_black.sh before ./black is present.