| commit | b3af4ff16877033adae4036de7857969152fadd9 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Tue Apr 02 19:25:23 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 02 19:25:23 2024 +0000 |
| tree | 3a7fe077d6d73575882b4e7aa45529b7d5934017 | |
| parent | 87a8f2443f2fe58346e163faec838b56dc29515f [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/8751745962458728161 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/ca48087e1df6a15082ec4fe9206021efc2abe569~..56a4b6ae743c0175d3568fe678d88f2f57c0048b ca48087 (olivernewman@google.com) [jiri] Include retcode in error messages 0e26cf7 (dthorn@google.com) [LLDB] Remove LLDB_TEST_USE_VENDOR_PACKAGES (removed upstream) f727aff (haowei@google.com) [clang_toolchain] Build LLDB for Windows amd64 platform 80d2c2c (haowei@google.com) [clang_toolchain] Enable LLDB Python support on Windows c66f590 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 01cac6b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 56a4b6a (haowei@google.com) Revert "[clang_toolchain] Enable LLDB Python support on Windows" recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/ca41f8ed2e8f261871e30f2582422021e9a7f2eb~..3868908180614e35f4b57e321e5e6f1de6adf7dc ca41f8e (mohrr@google.com) [python] Replace 'Optional[x]' with 'x | None' 53a614b (mohrr@google.com) [python] Replace 'Dict' with 'dict' c5580ec (mohrr@google.com) [python3] Remove remaining imports of six 9b90402 (mohrr@google.com) [python] Replace 'List' with 'list' 02f5ab0 (mohrr@google.com) [python] Replace 'Tuple' with 'tuple' 6027733 (mohrr@google.com) [python] Replace 'Union[x,y]' with 'x|y' 3868908 (mohrr@google.com) [python] Remove unnecessary typing imports 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: I1009a7f7ac483c358ce03a813ae9186f803f5541 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/201495 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> 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.