commit | 358875a3a9a657b64b725a50b300b22dedeb7031 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Wed Nov 13 00:21:00 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 13 00:21:00 2024 +0000 |
tree | acfeaa62cccc9ac9514c5e2ac1ef79d03a4be2a8 | |
parent | f670f16366943ad30fdc20a1f4e7e70ebf2523d2 [diff] |
bug_filer: Increase max age in build query Increase the maximum age of builds queried. This will allow bug_filer to see four full weekends of rolls in a row, which is useful since bugs are only closed automatically after three passes. Bug: b/377570481 Change-Id: I7f66d5c88b8a389ef50feaf1c63ac3cae3b66a1a Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/248472 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Taylor Cramer <cramertj@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-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.