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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/1e9821df4d0b94b61325d060da9c391e7b5c3d9e~..70d560572da2aa3595803d953fe3eee5b8fe2ad7
  1e9821d (atyfto@google.com)
      [cipd_to_git_roller] Wipe subdirs before ensuring
  79b6400 (olivernewman@google.com)
      Reland "[recipes] Use plain git for checkout"
  cc135a5 (atyfto@google.com)
      [fuchsia/build] Add output prop for assembly CAS metadata
  5c04cca (phosek@google.com)
      [clang_ml_training] Update ml-compiler-opt
  fd421c5 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  1ae4d6f (yuanzhi@google.com)
      [aemu] Upversion downloader, also stop downloading debug build.
  70d5605 (phosek@google.com)
      [clang_ml_training] Temporarily allow older libstdc++

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: I7c7fe385d20714872dc4ffc1d248a0f589b1c034
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/92816
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: a8296fa662cf3311400bd36cc87266f13d405106
  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.