Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (fuchsia) into this repository.

The build that created this CL was
https://ci.chromium.org/b/8829068240286293921

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/a3e2b06e6378901a7e90202e077e7f804988970c~..7be9bd78632f1c4a2e92da78e50da4424d8722ff
  a3e2b06 (olivernewman@google.com)
      [fuchsia_cipd_roller] Get project path from Jiri
  dee3521 (atyfto@google.com)
      [cl_util] Roll tool to latest
  c22b9cf (nmulcahey@google.com)
      [py3] Convert resource script invocations to python3
  889112f (nmulcahey@google.com)
      [py3] Run update_3p_packages.py under python3
  f163119 (nmulcahey@google.com)
      [py3] Run rust/x.py under python3
  488dfdb (nmulcahey@google.com)
      [py3] Run clang ml scripts under python3
  247fdfe (nmulcahey@google.com)
      [py3] Run clang-{format,tidy}-diff.py under python3
  2076151 (nmulcahey@google.com)
      Revert "[py3] Convert resource script invocations to python3"
  6522703 (olivernewman@google.com)
      [git] Add "checkout" nesting to checkout_from_build_input
  7be9bd7 (atyfto@google.com)
      [cl-util] Re-enable auto-rolls

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: I25520f6763822965c08865c8595568158ef6682a
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/71400
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: 5fdc08d659f192445be6638f3f728d24c1d4d953
  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.