commit | 26850d5ff15a03889f816748ad2dadb99a9b9214 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Thu Dec 12 15:09:08 2024 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Dec 12 15:09:08 2024 -0800 |
tree | 9122c8aa16a5d4b04aa243730f260c1a20f6a80f | |
parent | d9770a2bb2bff6da78348e890977b7f15280f508 [diff] |
roll_commenter: Move check to more logical location This results in a timing diff since we add to test_submit_time between the old and new locations of this block. The post-process checks have been updated to match the new behavior rather than making this test exactly like it was before. Bug: b/369718402 Change-Id: I486298bd29f98111124446995a142b7932911abc Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/254139 Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Ted Pudlik <tpudlik@google.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.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.