| commit | 11f0924d80e20a412bdd51a108f2d5bb65aad6f9 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Nov 02 22:06:45 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 02 22:06:45 2023 +0000 |
| tree | 550e81073351b47df4092632d6acb4f707b8d92a | |
| parent | 83037dc76313d5f8091309fd90d583867e30ff26 [diff] |
Roll recipe dependencies (nontrivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (recipe_engine) into this repository. The build that created this CL was https://ci.chromium.org/b/8765505561865133073 Please review the expectation changes, and LGTM+CQ. recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/bc823506675bfff173e2af808db497d7c11a484c bc82350 (iannucci@chromium.org) [recipe_engine] Switch recipes to execute with python3.11. 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. R=mohrr@google.com, tpudlik@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I8b6f8506b8771e54dd7e14a55a6a6639c50a9f33 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/178814 Reviewed-by: Rob Mohr <mohrr@google.com> Commit-Queue: Rob Mohr <mohrr@google.com> Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.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.