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/8697538786440675489 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/0f161770dd47ab96d499bf2b4401b53100f5a39f~..9cc618ba88aca505ab4aedb42cbf2a4626bd132c 0f16177 (haowei@google.com) [toolchain_cipd_roller] Add option to tag the rolled package 998a067 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 9cc618b (carverforbes@google.com) [testsharder] Change implementation of should_skip recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/66daa985819263cc9c90453dc00b412c9a632a70~..e0473ea34027c403e310525a2ad0473cc95a14c6 66daa98 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 51748c9373bd to 7defb40e58ef e0473ea (mohrr@google.com) [recipe_deps] 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: If3e7709379775d2480c845cd39a7aefe25b50dca Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/347912 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.