| commit | 1e2d0850b761a8181abb69700cd446ed906920fb | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Tue May 03 04:54:18 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 03 05:51:47 2022 +0000 |
| tree | bf3f2b0436a99d465173f87948dcfea1a09d0726 | |
| parent | 9fcb0c07b7d761f434ac4ea36964e1b5c319d2ec [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/8815214280355943441 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/d8b8ffe66ecfc000fe710f4118922bcd1f6b77d5~..d2e98680a6e796171f45753d668bab20ec4b685a d8b8ffe (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest 4a64121 (olivernewman@google.com) [fuchsia] Only update "latest" assembly inputs ref in canary d2e9868 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest recipe_engine: https://chromium.googlesource.com/infra/luci/recipes-py/+/50cbd4441e5f0efa0509a27d9330ce9f928ee590 50cbd44 (meiring@google.com) [recipe-py] roll recipe_proto 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 Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I190b5ec17407b194956ec5ae2135657baaad1a6e Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/93440 Commit-Queue: Recipe Deps Roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> Bot-Commit: 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.