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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/1a1f099c75c304a68fc0c2cdca6d2a14891bf555~..86ea4fc1a69b956f5015ecfa9f3dd77d115eec6d
  1a1f099 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  b0c066d (atyfto@google.com)
      [platform_version_roller] Adapt to new JSON format
  6b2df5f (danikay@google.com)
      [disabled tests] fixing bug for interpreting whether or not dis...
  8380ba7 (olivernewman@google.com)
      [btu] Allow dest="." in CIPD upload manifests
  86ea4fc (olivernewman@google.com)
      [tree_closer] Reopen tree outside working hours

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+/edc3cd1e9d177fd0ae245fbb9d25e141191add5f
  edc3cd1 (nicholasbishop@google.com)
      walkthrough.md: update test specification style

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
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: I72533b65c840fde70fbbc113446cc618ae5db3e8
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/95921
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: 601cd3541e83dcdbb73c4bafab1e7deb385a9762
  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.