commit | ca1e1457fdba0369ba35a8ec5707a894174e4c80 | [log] [tgz] |
---|---|---|
author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue Apr 26 06:50:48 2022 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 26 21:24:43 2022 +0000 |
tree | cd18a286b690c470b8d49d0a87f569d7a41fe980 | |
parent | 0c74d9ee9b937740c6dcb48ba3b5c42f50e4163a [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/8815841082529855857 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/254477061b5644cce6b1690465136d05c404ea56~..3e6724c9020c568ddae34b5ab60c66127aad47b2 2544770 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 6c5661b (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 08c3a66 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 22691f9 (joshuaseaton@google.com) [qemu] Explicitly specify an xcode-supplied linker on macOS 372c12e (haowei@google.com) [clang] Upload clang toolchain to CAS before running unit tests fa43a8f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest d1ca24f (haowei@google.com) Revert "[clang] Upload clang toolchain to CAS before running un... 3e6724c (atyfto@google.com) [binary_size] Recommend size rotation for absolute budget failures recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/6345fb20c97d488a7578d0fb58edd9b3a462448a~..36be9467fd4479eea43fc5bc8ae4043c984cf575 6345fb2 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from 4f40f26f3102 to 2aa3d7e5e866 36be946 (iannucci@chromium.org) [python] Deprecate api.python.__call__ 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 Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: If25428d90e5f5501289d137bd284243afeb84b90 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/92480 Bot-Commit: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Commit-Queue: Ted Pudlik <tpudlik@google.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.