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/8716842498521313777 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/3cb2885ec636e8b010fb6eb31bfb952c7074b5d8~..2ebdcb5eab53c73cc8562104466ef1551e49aa93 3cb2885 (danikay@google.com) [recipes] ensure that changes to jiri manifests don't skip testing 528e69f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 721db96 (olivernewman@google.com) [gds] Simplify + clean up tests c8fc87f (olivernewman@google.com) [git] Add read_commit_footer_multi() function f30a954 (olivernewman@google.com) [roll_comment] Support multi-repo rolls c342b33 (brianaberger@google.com) [cipd_util] Check uploader against allowlist. 698ffcd (ihuh@google.com) [checkout] Add query_params to get revisions for dependency CLs. 0ce1638 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 1a14f50 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 386e3fb (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools f7c8f1e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 2ebdcb5 (olivernewman@google.com) [gds] List number of labeled changes, not processed Please check the following references for more information: - autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller - rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback - cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I926e0c080021e943d60d7c311e65cad13502391a Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/285813 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
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.
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
./presubmit.sh runs three different sets of tests:
./recipes.py test train)./black --diff --check .).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.