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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/37daef9dbea12dce86d93833c219182fec5adf31~..0c7ce2bc160cc4bd48686c40b14eb1d9f4101d7b
  37daef9 (danikay@google.com)
      add column to identify whether a disabled test is compiled or n...
  dd5bb98 (olivernewman@google.com)
      [build] Add a test case for skip_unaffected_tests
  aa72b6e (olivernewman@google.com)
      [testsharder] Log input files
  5506143 (phosek@google.com)
      [clang_toolchain] Stop building runtimes separately for Apple S...
  21843ed (olivernewman@google.com)
      [build] Inline postprocess_build function
  0c7ce2b (olivernewman@google.com)
      [testsharder] Delete `mode` arg

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
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: Ic390cd1500979ca81843ba2fed2f07609dba6e3c
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/95220
Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com>
1 file changed
tree: 4fba182ea38a7fa44ff97e5b7785362ebc4d5b9a
  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.