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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/1c20e5946fdecc0990e1b0f39d6f42cdc7ad7188~..442fecbfd1eb67dba34cef1ec0ba246b4be4a8d9
  1c20e59 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  f8976e4 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update pinned tools
  7087510 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update coverage pinned tools
  ebcc4e7 (davidcorvaglia@google.com)
      [hardware_validator] Fix bug of zero tested targets
  df13935 (joshuaseaton@google.com)
      [android_artifact_downloader] Remove v1 properties
  fdd31dc (michaeladeniyi@google.com)
      [hardware_validator] Added service account as a property.
  442fecb (joshuaseaton@google.com)
      [android_artifact_downloader] Add support for "source" artifacts

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/2f6cda12c7971988687627743b7c4b212c3c42ee~..b6155985b85ef0377a82bf733a81f8b2de8eb752
  2f6cda1 (mohrr@google.com)
      [GEMINI.md] Initial commit
  13fe560 (mohrr@google.com)
      [engine_types] Add type annotations
  2ea6f92 (renewitt@google.com)
      [bcid_verifier] Adds additional context about ResourceURI.
  8dd95a4 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from b42c4f73ce49 to 72fca4949e39
  b615598 (mohrr@google.com)
      [futures] Add type annotations

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: Ie9e9d093a6ebbdf54c43139db26c86bc6315eca0
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/311102
Commit-Queue: Rob Mohr <mohrr@google.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
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>
1 file changed
tree: f927b63d6fafa13bf106a95a4d2a48c2f588da92
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. .aiderignore
  6. .editorconfig
  7. .gitignore
  8. .style.yapf
  9. AUTHORS
  10. GEMINI.md
  11. LICENSE
  12. OWNERS
  13. presubmit.sh
  14. pyproject.toml
  15. README.md
  16. recipes.py
  17. shac.ensure
  18. shac.star
  19. 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.