| commit | 7f8b72bedafab1d1f36ee2d885e678ad001a0ffc | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu May 25 09:30:34 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu May 25 09:30:34 2023 +0000 |
| tree | 3e58a16496904cbcecf4cd15849acd76fe612135 | |
| parent | b235af9b415fa6e2607b53b0fd89cee737ec3cd6 [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/8780140585744985025 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/4eb5c4defd6f9029624c8229489d2937f5fd9f75~..f06eddc3263a28f6ad9f4080ec8febfb08e65358 4eb5c4d (olivernewman@google.com) [shac] Improve function naming check highlighting e1cce59 (atyfto@google.com) [btu] Only attempt to run tests when testing pool is set febd601 (olivernewman@google.com) [shac] Add check for recipe function ordering a2fc1be (olivernewman@google.com) [cmake] Run black 9393cc0 (olivernewman@google.com) [checkout] Increase Gerrit replication lag tolerance efa8071 (catduncan@google.com) [android_artifact_downloader] Fix artifact transformation logic d078a56 (josephry@google.com) [firebase_docs] Use correct python binary 95971fe (nmulcahey@google.com) [macos_sdk] Use min version logic to select xcode ac9841b (atyfto@google.com) [artifacts] Roll blobfs-compression tool to latest 2cba87a (atyfto@google.com) [build] Make "upload artifacts" step nesting neater f06eddc (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/ca8108133477b427170bee7494866a934a0a0fe8~..7f9b133838f1240a537916677161afd8129b234f ca81081 (vadimsh@chromium.org) [swarming] Update `swarming` CLI tool. a5c25e8 (iannucci@chromium.org) [recipes.py] Unset PYTHONPATH in case users have conflicting va... 7f9b133 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from edf7c1502de4 to 406fda74bafb 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: I89e60c5cf61a153298a444b5879347c079747bc6 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/148871 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.