commit | 043bf112b268a89af6b65a23d3f417ec58973ab6 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Jan 31 21:23:54 2025 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jan 31 21:23:54 2025 -0800 |
tree | e8b6d4b012be3b81969138a92bc47c5af8921965 | |
parent | 27c1c5d0e405fc86f902de08ca5720938c3cce3e [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (fuchsia) into this repository. The build that created this CL was https://ci.chromium.org/b/8724166511026331521 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/63990ead3dac362d505a7c42159e7f9c35adf1b0~..13663bf253ad880433818a083dca0a5413e9e798 63990ea (danikay@google.com) [recipes] Fix bug in fx lsc message for lsc suggester recipe 5a31f26 (olivernewman@google.com) [submodule_roller] Make submodule_path prop required 4f01afc (danikay@google.com) [recipes] Turn off email notifications for dashboard commenter 877375a (frolv@google.com) [bloaty] Pass ninja path to cmake invocation 100162a (haowei@google.com) [rust_llvm_trigger] Fix some issues in rust_llvm_trigger recipe. adfa542 (danikay@google.com) [recipes] don't add to attention set for dashboard_commenter 13663bf (haowei@google.com) [rust_llvm_trigger] Prevent rust_llvm_trigger from inheriting b... 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: Ibdfccea84236b608e8a214a8d5b977f747ce1a2f Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/264093 Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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.