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/8697270759974103441 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/df02168bba2cf3d99b817bda2ecaae386ded2c9e~..7eb8b0e720699ef3a39414564536971fa3ad6777 df02168 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools dd79664 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 7eb8b0e (carverforbes@google.com) [testsharder] Replace the summary field with summary_if_skipped recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/ed7a3b07e2c2ca2f8b83d1f9684459daf28ed612~..b0770b386a663b91a1158c01bf0fff7ee53fed4d ed7a3b0 (mohrr@google.com) [post_process] Add annotations b0770b3 (mohrr@google.com) [proto_support] Add annotations 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: I9ba3c31926efbd1957ada882ef091e1c5a7fe8e2 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/348812 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> 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>
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.