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

fuchsia:
https://fuchsia.googlesource.com/infra/recipes/+log/bc0cda67f5969e60ce72e2510777c594b4d3a72e~..e097076e1e8a8dc4763a7c8c452c3451342b7741
  bc0cda6 (olivernewman@google.com)
      Reland "[sdk] Use prebuilt python interpreter from checkout"
  834a39a (atyfto@google.com)
      [cherry_pick] Replace api.python.*_step with RawResult
  6f8eedc (atyfto@google.com)
      [create_branch] Replace api.python.failing_step with RawResult
  f3c83cd (atyfto@google.com)
      [snap_branch] Replace api.python.failing_step with RawResult
  528192a (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com)
      [roll] Update tools to latest
  a05d7c0 (atyfto@google.com)
      [milestone_roller] Replace api.python.failing_step with RawResult
  6c82e9a (atyfto@google.com)
      [recipe_bootstrap_test] Replace api.python.failing_step with Ra...
  aaa8710 (theosiu@google.com)
      [recipes] Switch docsgen to generated_docs json and remove fire...
  d9fc149 (atyfto@google.com)
      [publish] Migrate publish tool usage to recipe module
  6d890de (haowei@google.com)
      [goma] Use python3 for Goma unit tests and packaging
  6f7a44e (yupingz@google.com)
      [submodule_update] Remove duplicated fuchsia checkout
  e097076 (haowei@google.com)
      [goma] Remove python module from goma module

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py/+log/2d175f792d290c8035dfc05dcc29cfcae177a351~..5d9f8ec132fb61d90c59ad600a5c68cd980871ec
  2d175f7 (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 850560a1a20e to de048fb36dbb
  58d2894 (tikuta@chromium.org)
      swarming: do not use latest package
  5d9f8ec (chromium-autoroll@skia-public.iam.gserviceaccount.com)
      Roll CAS Client from 672cf8a2c1d3 to c133751cba7b

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
Bugdroid-Send-Email: False
Change-Id: Ia0077930d772d801d2ce6ae8660220c691cc7644
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/67681
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: 9ce2f1a02f08d5b61f56ea6804c2ec3ef6937a33
  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.