commit | 8e105a193f7d6508cffe15bcf780997721a607de | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Wed Jan 29 21:14:43 2025 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 29 21:14:43 2025 -0800 |
tree | 883f34ded1848f172e237925de48b78b9d3736e3 | |
parent | 023d1af2d4f78fafbf2e924b4db8915c430b47b5 [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/8724348390990311105 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/75f478271bd89d45a8928add3ed9d784a1a83388~..459e81485322b04ab4abebc4bea6827a42f07dcd 75f4782 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 9803afe (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 4efaf9f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 459e814 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/6132401d7c897d9cde6eb958162d635568215f2b 6132401 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from be208752faa4 to c36fd1e86ba4 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: Ie3663f01e03f6989dd9ebe5671527f1803853683 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/263440 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.