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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/1035cbddcb0164f80fdc33f8db693a0a8c715381~..838bd72478a01a4c012fc4df836c066663058443
  1035cbd (mohrr@google.com)
      [git_roll_util] Add filtered tags
  c500a91 (haowei@google.com)
      [clang_runtimes] Pack runtimes and upload CIPD
  f75bf13 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  05323db (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update coverage pinned tools
  1a25321 (haowei@google.com)
      [clang] Allow clang base builder to trigger the runtime builder
  bf46ecc (carverforbes@google.com)
      [test-centric-dashboard] Create recipe to link dashboard to CL
  838bd72 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+/e7d8f4656b7715829812e78a97062d5aa861e627
  e7d8f46 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 69a01cccf677 to 17620695ace4

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