| commit | 605d5397aea45d2bf24b298028d62400703d713a | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Sep 26 09:33:05 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 26 09:33:05 2024 +0000 |
| tree | 973223c03222cbc380ae21cd9b8fbf75d02c40af | |
| parent | 70699d86a8cbbbb6b91f5a612ac6d511a5ff59c6 [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/8735748048465286785 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/f3fb317cc9b26b6320458502634d0953988298f3~..35027f319373f9d183a3f41b72ca47baf046c221 f3fb317 (olivernewman@google.com) [cherry_pick] Update recipes.git manifest TODO 4079b6c (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 9612fce (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools a8ede69 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update coverage pinned tools 35027f3 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/22465a93fddf5dc0b244871bbfc65e2b80850211~..9b0304704d591355f13053a00a9aa5c11d1518bb 22465a9 (mohrr@google.com) [step] Warn if api.step.nest() name is non-empty 2239d34 (iannucci@chromium.org) [warnings] Add ability to forbid warnings in downstream repos. 488d17f (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 703841c4a3ff to b71f61522497 6e9a4a1 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from bdc7b5e9de82 to 27dbb861b157 9b03047 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 27dbb861b157 to 81b96921c2c4 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: I8704af3f4b323bc6f0c4f5a6cf0285a5e10b0c6e Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/238019 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.