| commit | 67d72302c0103ba42c1f252d50f885d5132c4848 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue Jan 25 06:50:58 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 25 08:55:19 2022 +0000 |
| tree | c469ce9ae0fcdd1583aeb7e3d226460ed4ca3634 | |
| parent | 767a5ba447c19a25bcd642e8d1d4088f02833f83 [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/8824085406294657761 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/6b6c06756c07515e196e19e531ff0775be73b8cf~..d8281dc8337b97de02026b051fff2d08c0c453e5 6b6c067 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 9ba8f11 (olivernewman@google.com) [artifacts] Don't infra-fail if build was cancelled 0b8f4f5 (atyfto@google.com) [create_branch] Allow empty commit post-config gen 20cf3d4 (yupingz@google.com) Change snapshot_path to include all ensure and version files 60e831d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest e73ef8d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest e8554cf (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 20ddf0f (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest afa034d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest f9454f8 (yupingz@google.com) Remove snapshot_file 11a4785 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 6d2bd74 (atyfto@google.com) [git] Add helper to cherry-pick a CL 2ea2f23 (atyfto@google.com) [checkout] Slightly generalize _apply_patch() d8281dc (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+log/312823d273286a0cf42514f5d00633262ee92f65~..a476355d81d68d946bb2ab2b9431d648e7ad2167 312823d (bryner@google.com) Convert git stdin/stdout to and from bytes. a476355 (chromium-autoroll@skia-public.iam.gserviceaccount.com) Roll CAS Client from a169f70aa54e to 09f8b3edbbf1 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: I861bfcbf0fdf3b7fe954a1df26f6361bff112bcc Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/81360 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.