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/8669770001315785825

depot_tools:
https://chromium.googlesource.com/chromium/tools/depot_tools/+/f8d44cce2ee508274f018d1bc0afb4754ed974f8
  f8d44cc (agrieve@chromium.org)
      Concurrently fetch the CL description in "git cl presubmit -u"

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+/89143c642ec28b2a5dac98e4ffd41c53ef9e10b6
  89143c6 (betramlalusha@google.com)
      [recipes] Adds openssh binary to recipe

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: Ib687b6857abf617e5d93d0af3e35e58d855ded0d
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/484749
1 file changed
tree: 83834ba31d64bbc76d2e715247c5d58d3a5246bf
  1. .agents/
  2. infra/
  3. recipe_modules/
  4. recipe_proto/
  5. recipes/
  6. scripts/
  7. .aiderignore
  8. .editorconfig
  9. .gitignore
  10. .style.yapf
  11. AUTHORS
  12. GEMINI.md
  13. LICENSE
  14. OWNERS
  15. presubmit.sh
  16. pyproject.toml
  17. README.md
  18. recipes.py
  19. ROLLER_OWNERS
  20. shac.ensure
  21. shac.star
  22. 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.