commit | df604fd7a4bc3f771eda427db403c638744220db | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Wed May 15 17:23:13 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 15 17:23:13 2024 +0000 |
tree | 905e2d43fc93d8bafe569bfd2bf48a749135c696 | |
parent | 02a4418915c455eaeb914474c6b6881b90029e61 [diff] |
dev_status: Increase max age Increase the default max age so we're more likely to get 10 builds for infrequently run builders. This means we'll get more falso negatives, but that's better than getting false negatives. Bug: b/339638439 Change-Id: Ibff2a39181edbdb931e2a93291732df273c9d45e Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/209978 Reviewed-by: Taylor Cramer <cramertj@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.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.