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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/f732778c23c38b87d891a9a843622db307d4af43~..36d27989e2fe4bc7bf0657511fbaa1adaccf4569
  f732778 (olivernewman@google.com)
      [subbuild] Retry subbuild scheduling
  58a93f9 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  acff25f (mohrr@google.com)
      [recipes] Switch to proto-based properties
  8fb84ad (olivernewman@google.com)
      [scripts] Fix props_to_proto's default property detection
  c571461 (haowei@google.com)
      [goma] Use 'integration' ref
  36d2798 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/cd746d1b2dac325c3f1c639a9dff682ce80698ec~..47014f5afcfba6c0c03cd160ef690ef431a49f22
  cd746d1 (bryner@google.com)
      Update to fixed cryptography 3.3.1.
  32d7da9 (godofredoc@google.com)
      Allow overriding bot_id in the swarming test_api.
  b35cc6b (gbeaty@chromium.org)
      Don't enqueue the py3 version of a test until the py2 version c...
  4f0aa33 (godofredoc@google.com)
      Use bot_id from env if passed by test_api.
  47014f5 (tikuta@chromium.org)
      swarming: remove with_server

More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug.

R=mohrr@google.com

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: Ie1cc75f37e0bfa36953d7aa2ad20fd752f1042d7
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/68283
Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
1 file changed
tree: d5c1c5eb177e9e22bb7604f9bca8f9d9c4f9d09d
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. .gitignore
  6. .style.yapf
  7. cipd.ensure
  8. OWNERS
  9. presubmit.sh
  10. pyproject.toml
  11. README.md
  12. 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.