| commit | a2250688eea61fe085fedec361124c78f9c70a65 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Wed May 15 17:48:57 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 15 17:48:57 2024 +0000 |
| tree | bc58431a8bdaaf91f60c0a7b9d8745b5c719b4d3 | |
| parent | df604fd7a4bc3f771eda427db403c638744220db [diff] |
dev_status: Tweak defaults Increase the number of builds requested, reduce the minimum number of builds for comparison, and reduce the max age. The max age increase will ensure the dev builders being compared are more likely to come from the most recent image of dev. Increasing the builds requested gives more of a chance for something to pass. Decreasing the minimum number of builds lets more builders be compared (and not excluded because because there aren't enough recent builds). Bug: b/339638439 Change-Id: I95e43d709ffe333349408fdae817247c9528dad8 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/210034 Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Reviewed-by: Taylor Cramer <cramertj@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@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.