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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/60d17364545320de0b8cf8e6cdecff3a4a48a2aa~..ba3870e158802deda212131675914a8ba41f5889
  60d1736 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  74a3956 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  62a060d (olivernewman@google.com)
      [build] Move out compdb filtering logic
  5760e93 (olivernewman@google.com)
      [build] Delete stale test case
  8fd199a (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  199419f (jessicacgu@google.com)
      [fxt] Add test links to appear in the launch step.
  ba3870e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest

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: Ie2bff8db9d8f2ca0427cb4cf49abc9a22074155a
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/89361
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: 085434c0ae08ad66b7480e8d78b6e6ef45fa061d
  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.