| commit | b8111b7827ab0a8830602676b5117164443c7383 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Oct 27 15:49:21 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 27 15:49:21 2023 +0000 |
| tree | 7c7ca31fa2c53fff1553ce02b771e7a394d09a2e | |
| parent | 2e6a9d028b44c25addfcd7c13bae3684377d08da [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/8766074155745766033 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/0b4c08c8ca956b91442623a76a41fbbe49c922a9~..e17708d32505b197eaa48c81dfb327a213c73d18 0b4c08c (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools e17708d (mohrr@google.com) Use new defer module 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: I63668047d084871984c1aaf1605479866c1b4048 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/178071 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.