| commit | b910ec9126159d268fabc6eb9705d13dafed4de6 | [log] [tgz] |
|---|---|---|
| author | recipe-roller <recipe-deps-roller@pigweed.google.com.iam.gserviceaccount.com> | Mon May 30 22:26:36 2022 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 30 23:04:15 2022 +0000 |
| tree | 83133cb631e47afce39110c678d1cb19526f134f | |
| parent | b257b63d7b1254109e7c7becf0974135cafc8264 [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/8812701973047139569 fuchsia: https://fuchsia.googlesource.com/infra/recipes/+log/2b5d8daf22ae151f24a4959e77ebf3af5bc1a1a8~..2880594e3b4fefa9d477931b0c54362e6beddea9 2b5d8da (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest eaefe87 (phosek@google.com) [clang_toolchain] Use cleanup dir for XDG_CACHE_HOME b4e538a (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest aeaf9be (atyfto@google.com) [fuchsia] Add placeholder for toggling binary size enforcement 2880594 (global-integration-roller@fuchsia-infra.iam.gserviceaccount.com) [roll] Update tools to latest More info is at https://goo.gl/zkKdpD. Use https://goo.gl/noib3a to file a bug. Recipe-Tryjob-Bypass-Reason: Autoroller Ignore-Freeze: Autoroller Bugdroid-Send-Email: False Change-Id: I27649a632abc5608a455d10092d4caeec622d543 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/96480 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.