| commit | 0aa92c2b71ccb350d3b9753f3c2c91d74184be45 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Sat Jun 03 01:16:58 2023 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jun 03 01:16:58 2023 +0000 |
| tree | 071bb2baba6a0f19c59cf00763bd7cd682b9ea71 | |
| parent | 041100517588c9a3248aa9c12d7b153ede18e711 [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/8779354679657369441 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/e11dcfe33a027347ce9c304ab731fe59cda169f6~..dd02333155d4606a7cb9be4e1bbddc727fbfe819 e11dcfe (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 240db57 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 4f34451 (andresvi@google.com) [cipd_json_roller] Add roll_options property. e5facff (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools db8c0d1 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 390c5bd (atyfto@google.com) [sdk] Add no-op "sdk_subbuilders" property ae80106 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools 904c802 (atyfto@google.com) [sdk] Remove convention-based derivation of subbuilder names 9157a99 (tmandry@google.com) [rust_toolchain] Add thumbv7m-none-eabi target ffc4610 (gulfem@google.com) Use tempDir for -debuginfod-cache dc949fb (andresvi@google.com) [cipd_json_roller] Remove roll_opts overwrite. dd02333 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/69ab1e1e475d8948f77ad639199af449ed190be0~..e698b49d3e82e1c0bb9bf0a1265d83f34c51d318 69ab1e1 (iannucci@chromium.org) [doc] Add a --check flag to exit 1 if the doc needs regen. e698b49 (gredelston@google.com) post_process: Add StepCommandEquals check 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: Ifa6688044829c063ca8ce4fe56104a72fa67dbae Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/150410 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.