| commit | 5d4d47fda5800e9a3d6e4d7330f6887486e713a1 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Mon May 13 18:05:49 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 13 18:05:49 2024 +0000 |
| tree | d9e5d4635a75078f8862e9654d431ad5b066f2a0 | |
| parent | 5d67fefc6d3b31beecac0ac6620735d5c4d69efa [diff] |
dev_status: Exclude shadow buckets Exclude shadow buckets from evaluation. Shadow buckets are only used when running tests with led, so we don't really care about whether they are working or not. Instead of hardcoding "shadow", use the fact that shadow buckets don't have any configured builders. This may exclude other buckets as well, but if those buckets don't have any builders we don't really care. Bug: b/339638439 Change-Id: I52fb8d55a160fa980de7d88240d6998b84f2ccea Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/209545 Commit-Queue: Rob Mohr <mohrr@google.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Reviewed-by: Ted Pudlik <tpudlik@google.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.