| commit | b3b266604a9a0091f846ce6b2c8061da38f5a6c1 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Fri Apr 01 06:56:01 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 01 07:57:01 2022 +0000 |
| tree | 3c85d748e13820b8a9c6dc54428e2375880253e7 | |
| parent | 3a4e118fea4e048f66906dbb5d5966837bb800ec [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/8818106007715414801 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/06fc5433b90cd6f277c08d63bf16f0b24c00b111~..c34d25a20093a52eefafb72a926a28d96334234c 06fc543 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest fd26a3e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 2e8c9aa (dkoloski@google.com) [rust][toolchain] Ungate target test suite on arm 1cb0ada (yupingz@google.com) Add git status to submodule_update 90eacb6 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 003ed3b (dkoloski@google.com) [rust][toolchain] Add command for debugging tests 2f8beb4 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest b9a2f8e (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest efee564 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 2620b92 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest f1a915b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest c0260c9 (ihuh@google.com) [testsharder][proto] Add flag to add image deps to shard deps. 39e448f (dthorn@google.com) [Clang] Use static Windows libc for deps with old CMake. 5056bc7 (yupingz@google.com) Remove CQ+2 from auto_roller push 5da4baf (ihuh@google.com) [testing_requests] Add zbi_image to botanist command. c34d25a (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/83eab4616e574eacf659d42648b60f449db6d44b 83eab46 (whesse@google.com) [buildbucket] Relax type check on buildbucket ids More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=tpudlik@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: Ic1de829b6742f8f73b182547313f7e0db4646ac7 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/89523 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.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.