| commit | be6d35548292a26035c7bd5bc0affc018dc21d55 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Mon Oct 21 20:17:35 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 21 20:17:35 2024 +0000 |
| tree | 15b46b2de3ad362dfa055167bfd2e40bd8e89193 | |
| parent | 0ba8c4d58f784a860360d21959d95b5f8e4e9053 [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/8733442305781522753 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/60d13ad067dbd4226a99aae287d7f3dc320f1701~..51d6f26ca6a65babf1425af4a93d72f6110e14c8 60d13ad (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 123fe76 (ihuh@google.com) [testsharder] Read testsharder_params so it shows up as a step... e0f7940 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools a3392c9 (paulkirth@google.com) [clang] Remove workaround for LTO'd tests in stage2 builds 70c54a7 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 23404de (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 9209983 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 51d6f26 (olivernewman@google.com) [spec] Clarify `use_tcg` field recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/617849eadd067159da8bba4fdecdc9351cbac15b~..c657bee1e545b90f1582384979faead8769a6621 617849e (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from ad209d9a27e1 to d212e392e327 c657bee (lgrey@chromium.org) Fix find and replace fail 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: I9ee1ecad29558cce06781b8538a9f4c832bcb1be Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/243712 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.