| commit | f7607e3fc80d6b5146226705d3387f3636fb0fd5 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Oct 04 23:27:18 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 04 23:27:18 2024 +0000 |
| tree | e2174be13187fa5c8732c806d1219e917dbe5bc8 | |
| parent | 9333ff5ffbd98a5ab08d232ca3acb4150c82bb97 [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/8734976776882885265 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/7b9e67216b37f4a581aa6fda06845e22daed8127~..efcf1be838bb397c9cf9923f59379d60526ad9d7 7b9e672 (joshuaseaton@google.com) [testing_requests] Add support for crosvm test tasks 20a4348 (ihuh@google.com) [testing_requests] Add SYMBOL_SERVER_URLS env var. 283adb5 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 450df01 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 35c5087 (mohrr@google.com) [builder_status] Assume the current builder exists 91f2f50 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 04be3b6 (mohrr@google.com) [auto_roller] Use "presubmits" not "CQ" in message 1a22261 (tmandry@google.com) [rust] Update PR search b6addfe (tmandry@google.com) [rust] Don't apply patches in newllvm builder efcf1be (mohrr@google.com) [gerrit_auto_submit] Look up tree in CV recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/2c1fb9cdba0015905efaf4c0965a562bfb8580ca~..f22bb540ec02068b2211f1fe3671ca859d768a75 2c1fb9c (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 7f3ede4bb1fb to dd13340e3303 f22bb54 (mohrr@google.com) [change_verifier] Fix argument order 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: Ide5f8e07308e8d0399e36afb7fb4f95e24193fc8 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/239942 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Austin Foxley <afoxley@google.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.