commit | 78edbd07b9614314f1c4cd57ac9e96c072ef42f9 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Wed Mar 23 16:08:16 2022 -0700 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Mar 24 01:01:15 2022 +0000 |
tree | 9ed7f6eb43adebba52a058e8a905508ec7de371c | |
parent | 937a5aa91922da921003f1b9a6016df37c0c3dd9 [diff] |
cleanup: Use concise super() everywhere This is a more concise version of the `super()` call that was introduced in Python 3, which we can use now that recipe code doesn't need to run under Python 2. Change-Id: I0da7bdadf804e917ec6cc39164e5f54fde9e5040 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/88960 Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Oliver Newman <olivernewman@google.com> Commit-Queue: Auto-Submit <auto-submit@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.