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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/38297128cb04725e7d07eff1cb11a60d535dce12~..dff8a71ba491f9622c9e2ff4b0caa9607b1e74ef
  3829712 (atyfto@google.com)
      [milestone_roller] Enable configuration for non-f milestones
  f31085e (lijiaming@google.com)
      [bazel][SDK] Materlize Bazel SDK symlinks before upload
  b1b2b4e (olivernewman@google.com)
      [testing_requests] Simplify significantly
  5e8daa0 (olivernewman@google.com)
      [testing_requests] Stop copying build_results
  79751d7 (ihuh@google.com)
      [testing_requests] Remove references to use-runtests.
  8fe2a9d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  e8b29a5 (atyfto@google.com)
      [docs_roller] Stop passing deprecated -S flag to gndoc
  dff8a71 (lijiaming@google.com)
      [bazel][SDK] Fix the temp dir for bazel sdk artifacts

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+/4ddc3eab0c2f9d8fbcc78caa12bca4ae21a79e1a
  4ddc3ea (funing@google.com)
      Add interpreter option for py scripts

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: I97c880604e2cba57ad0280b31546152712d4f007
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/126733
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: 778c36357b1db86894b1e06ed17b6b35220579ff
  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.