commit | 05925089bece2f9f62a6ec3e3adad90d3da8b2de | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Aug 06 21:17:25 2024 +0000 |
committer | Rob Mohr <mohrr@google.com> | Tue Aug 06 21:17:25 2024 +0000 |
tree | 7e16b01392a7210c02006ba17e86b6abbfe09c89 | |
parent | b97f2526eba6a168c10de21e855a41007b2a3aec [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/8740324952767935057 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/8a4b2a5c656a64b642c2046881d3739c2fe9baac 8a4b2a5 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/2fce2a15ca35063f0344117d8069111fc4b9da2b 2fce2a1 (mohrr@google.com) Roll recipe protos 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: I4de67c4ad9c744fcc2853e560856b5246253adee Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/227851 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.