| commit | 4eaeb806781a5c1dcd5eae35846fb41ca46cba65 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Fri Sep 20 19:00:59 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 20 19:00:59 2024 +0000 |
| tree | 0a73de8c89ed87bede4ed39613ec7f9863480f87 | |
| parent | 4d8a7f7bb8a8ee9a809706fdd3af25ba78ed70cc [diff] |
abandon_old_changes: Initial commit Abandon old changes owned by the current service account. This will help clean up rolls that were orphaned by rollers. Cap the number of abandoned changes at 10. This should be enough to get through all the past changes without taking too long, but it's still low enough that it won't delay the rest of the builder more than a few seconds. Bug: b/368181572 Change-Id: Ib243b38a3b67eb8b1d10b8c004931b9a8b23478e Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/236838 Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Ted Pudlik <tpudlik@google.com> Commit-Queue: Rob Mohr <mohrr@google.com> Lint: Lint 🤖 <android-build-ayeaye@system.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.