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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/b8820199531208d6dc65daec81d5fba2c30c4486~..22e9533ab65faa1f75bf6408ec63d1b1367599e4
  b882019 (digit@google.com)
      [ninja] Enable verbose output when running tests.
  93cc012 (olivernewman@google.com)
      [static_checks] Use incremental cache for checkout
  b287ac9 (olivernewman@google.com)
      [shac] Allow builders to override entrypoint file
  4363cff (atyfto@google.com)
      [shac] Add shac_internal.star with cipd ensure-file-verify
  21d3c12 (ihuh@google.com)
      [coverage] Update name of cipd.ensure file.
  4a15d70 (dkoloski@google.com)
      [toolchain][rust] Use `previous` ninja
  810abbf (atyfto@google.com)
      [sdk] Fix CAS overrides naming bug for PBv1/v2 metadata
  6972869 (yupingz@google.com)
      [checkout] Add commit step to submodules
  4b6dad7 (atyfto@google.com)
      Revert "[cmake][linux_sdk] Switch CIPD floating refs to pinned...
  22e9533 (mohrr@google.com)
      [recipe_testing] Update deprecated led command

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/95f73e8159fcc74726e10f1553b8daabfd267bf6~..40747dc790b9f7c75640795c4ff3dd009daeb3d2
  95f73e8 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 45502e388ddf to fe20b089d931
  40747dc (mohrr@google.com)
      [led] Rename edit-cr-cl to edit-gerrit-cl in tests

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: I45e5905dc692a5ec9a6cb6944317ef0abbe9e192
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/172192
Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 7f8b45abc20a0a6b011a8de39bc06df71a4bde2a
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. .gitignore
  6. .style.yapf
  7. AUTHORS
  8. cipd.ensure
  9. LICENSE
  10. OWNERS
  11. presubmit.sh
  12. pyproject.toml
  13. README.md
  14. 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.