commit | 062b8303981d3c7893506e58214c82eebb18995a | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Thu Jul 20 13:56:17 2023 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 20 13:56:17 2023 +0000 |
tree | 53b3f67da300a44eccf13ec7a924868d2e7cc6c2 | |
parent | 510520deec34856dbd92c56fe311b7fe76be1a12 [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/8775048480489560705 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+/bc57d656b962a84f6be709b867d60163053b5c67 bc57d65 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update pinned tools recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/58526aed06cb07fd611c5c6da38df67d5c162f1b~..c9aad4d94e4210dadc962bd0104b5a4444850fb1 58526ae (iannucci@chromium.org) Remove WARNINGS from recipe_module_importer. fdfaa9c (iannucci@chromium.org) [recipe_modules/context] Remove futures/six usage. 0066072 (iannucci@chromium.org) Remove DISABLE_STRICT_COVERAGE from recipe_module_importer. de6b9af (iannucci@chromium.org) [archive] Clean up some py2 compatibility things. c9aad4d (iannucci@chromium.org) [recipe_modules/led] Remove futures/six usage. 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: I409f2429903752d774af98744619bc2b7cd32fa9 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/157390 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.