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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/493e7ebc7129e3615c5b28d37ed993987d482abe~..47b490e7c8bcd89b4fcf90b2484f92283062a8a5
  493e7eb (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  73c1a1f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  caea551 (jjosh@google.com)
      [llvm] Add "*CodeGen" libs for arm64 and RISC-V.
  47b490e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/beb06c62530d5ac91f5322d29e3980a647471333~..eb434718b27659fb36792b710cf2b80b8d85aa0b
  beb06c6 (chanli@chromium.org)
      [recipes-py] Roll LUCI proto
  cca5064 (iannucci@chromium.org)
      [warn] Increase scope of warnings to be process-global.
  5f06e1d (mohrr@google.com)
      [commands/test] Reduce threshold for long-running
  f1de410 (mohrr@google.com)
      [config_types.Path] Deprecate Path.is_parent_of()
  791c785 (chanli@chromium.org)
      [recipe_modules/buildbucket] schedule: add `led_inherit_parent`
  1ef4627 (mohrr@google.com)
      [config_types.Path] Deprecate Path.join()
  eb43471 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 7c520167d617 to 01d1863acbd3

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: I2b81761f7c9f98506f1bfc3dc7df1cd3553dc473
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/207377
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: 29f8839fa6850386512f6abb556c8cd1896a1b17
  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.