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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/5806ea60f98ad86357484e6400501d7c1d7c5d98~..362efff94098f9f865c3e0ccb94ad3906a0b31db
  5806ea6 (atyfto@google.com)
      [fuchsia/build] Leave FYI comment on CLs for size creep
  980ea38 (mseaborn@google.com)
      [proto] Clarify the meaning of the max_attempts_per_test parameter
  c173f14 (gbeaty@google.com)
      Remove use of the include_log argument to write_raw.
  282edac (atyfto@google.com)
      [fuchsia/build] Fix build URL reference
  362efff (chandarren@google.com)
      [recipes] Add extra ls-remote function to git API

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/4dcc60114c6afc0c17d17ca3813e5149799240f1~..74207fa63ab42cbee8d4afcb57de901a8f142ce8
  4dcc601 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 35f3f4525eec to 893bb89a656c
  74207fa (yuanjunh@google.com)
      [autoroll] Run again no matter which type of error is thrown

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

R=tpudlik@google.com

Recipe-Tryjob-Bypass-Reason: Autoroller
Bugdroid-Send-Email: False
Change-Id: I68c51b93ae7e7f70afabf7dce2deb75777eb7cb6
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/71624
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: d47ff2a5dcd8ce81de555b5cf8015f5e840ab7c1
  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.