commit | 3ca8d3b52cfc3bce77a459aa4565ac701f1077f3 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed May 22 10:47:01 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 22 10:47:01 2024 +0000 |
tree | 2881f749ea80672b2d13ac9853feeac6e62cef15 | |
parent | 1fc4e83a040bcaf04421082b1a0084deb0b268a4 [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/8747250086541682113 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/27ece063ede809579fd915c6503d67dab586db42 27ece06 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/ad79a5f376b89556f9e5cb86778f9096875426fd~..e7b7f04f2cd591f8be47b8859c87ae6ed167e383 ad79a5f (bpastene@chromium.org) Allow ancestor_ids to be set in buildbucket's recipe test helpers 2639a9b (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 54d5e5423ec4 to 6dd0c6cf2b42 61b570e (mohrr@google.com) [post_process] Update docstrings e7b7f04 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 17b46bce7733 to d8c41eecc02c 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: I0d698570049aa6bd6724c912e3d147810cb9de2b Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/210892 Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: 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.