| commit | f495261af02048c2771636c35ae6b7f76f56fab9 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Wed Mar 02 06:51:53 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 02 07:36:21 2022 +0000 |
| tree | 60230705fd29013ff73da1d5d9f1a12967102a11 | |
| parent | 7f541e0649c948d9194678e2c1726ec259c903ee [diff] |
Roll recipe dependencies (trivial). This is an automated CL created by the recipe roller. This CL rolls recipe changes from upstream projects (fuchsia) into this repository. The build that created this CL was https://ci.chromium.org/b/8820823915612465697 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/0cc520d8180fe1e60f50619702b738dfba28dfef~..307ade4bf3c866eb72ac4f992e65bb9d0f0babe2 0cc520d (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 5d22172 (olivernewman@google.com) [fuchsia] Emit `target_arch` output property 4107611 (olivernewman@google.com) [fuchsia] Copy build logs from subbuild 307ade4 (olivernewman@google.com) [build] Link to debug logs in GCS from top-level build step More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. R=mohrr@google.com Recipe-Tryjob-Bypass-Reason: Autoroller Bugdroid-Send-Email: False Change-Id: I8b5ac520def01568af15e0a00205979a30425a22 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/86000 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.