| commit | d2791b11a32150cf941dfcdec3ecd68dcb6558e3 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Nov 09 18:42:24 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 09 18:42:24 2023 +0000 |
| tree | 612c7742cd59dd4cd7650dd9bb9434a3668f642c | |
| parent | 1e40c2cd7f156565a9b03a0ae3a9fba49e046b58 [diff] |
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/8764888399697209617 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/f60d700e6c2449bc2e7a285dda8085b9bd3defe1~..b9442802d3b3a626a6e70fd709c5ab77828c86ae f60d700 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 28f496b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 2dc6196 (mbrase@google.com) [ftx] Remove disabled flags -name and -sdk-and-images 9298ee0 (hjfreyer@google.com) [fxt] Add link to fusion UI. de4b36c (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 26e356b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools d4d227d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools b944280 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/165afa51621c53e73e7dd81975ee5e30c5e8d081~..5aabe73071265c4ab2d474e3f94f21f3e680aefb 165afa5 (mohrr@google.com) [recipe_engine] Handle Exceptions containing StepFailures d084b4e (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 2baa055d4de9 to 38b65dfa7a0d 5aabe73 (mohrr@google.com) [lint] Remove --whitelist compatibility option 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: Ifc577ad042ed2538d032f1cbe0e4f560783890e0 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/180211 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.