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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/00620a5c7108bcd3f403b3064b0745e3d668fe6b~..3cf3995c3aaaf6338a9003da6dfb4993a59b5642
  00620a5 (danikay@google.com)
      [recipes] Add query and project properties for gerrit nudge recipe
  a7e16c2 (frolv@google.com)
      [bloaty] Set Rust linker to lld
  b6b76fa (haowei@google.com)
      [cipd_util] Allow multiple search_tag when uploading CIPD package
  ce69f55 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  dad3bdb (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update coverage pinned tools
  8222722 (frolv@google.com)
      [bloaty] Attempt to use clang/lld as Rust linker
  19e718d (olivernewman@google.com)
      [jiri] Delete unused fetch_packages method
  d11a63b (gulfem@google.com)
      [profile] Add search tag for CIPD packages
  af348c5 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  594829c (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  3cf3995 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/9d24599642adbd943e1d13c6d7b80c8961ce0756~..d7c6e2a03f9c1703a3eeadc45e7cafbf6ccbc252
  9d24599 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 8f3d9614016f to a9ef97b3c697
  d7c6e2a (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 31b74d4b167d to 1c8dc8e37a49

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: I5f1e29bf139762a11ca86e83c737da7aa7cdbd62
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/265181
Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 391fc4302cdca2e82b3ae37194ad2d2751d70b46
  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.