Roll recipe dependencies (trivial).

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

The build that created this CL was
https://ci.chromium.org/b/8673453009715826865

depot_tools:
https://chromium.googlesource.com/chromium/tools/depot_tools/+/13febbee9ece9e03df923f69d540afc63c6db93e
  13febbe (agrieve@chromium.org)
      Fix "gclient sync" not syncing --assume-unchanged submodules

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+/346a63ab1a227c759d771f1d14c9190204a9f0d9
  346a63a (olivernewman@google.com)
      [shac] Make cleanup_deps run as a shac formatter

Please check the following references for more information:
- autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller
- rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback
- cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md

Use https://goo.gl/noib3a to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: Icec32fa634873d333f79914fda805e0524f92016
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/455585
1 file changed
tree: 971ccbea468dac04f0b41a2bcc9fc2abded6b56a
  1. infra/
  2. recipe_modules/
  3. recipe_proto/
  4. recipes/
  5. scripts/
  6. .aiderignore
  7. .editorconfig
  8. .gitignore
  9. .style.yapf
  10. AUTHORS
  11. GEMINI.md
  12. LICENSE
  13. OWNERS
  14. presubmit.sh
  15. pyproject.toml
  16. README.md
  17. recipes.py
  18. ROLLER_OWNERS
  19. shac.ensure
  20. shac.star
  21. shac.textproto
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.