commit | 331a2d65a714d6b83c33be18b4843b64f6bb83eb | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Mon Mar 25 20:20:51 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 25 20:20:51 2024 +0000 |
tree | 0243b371ccc1e7f25c81e358caf3321ac13d9f92 | |
parent | cbe35e3e72a267a76a00cc479a177979c8cec357 [diff] |
luci_config: Drop expectation files No assertions added—the behavior of this recipe is sufficiently tested in the Fuchsia validate_lucicfg and Pigweed checkout modules. Change-Id: Ic72ef84f24de93a82e985ab1b7baccc236d6fe40 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/199612 Reviewed-by: Ted Pudlik <tpudlik@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.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.