commit | 338fbc56257c7e937d67cd00b8c30f1e63584df4 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Sat Sep 07 01:12:52 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Sep 07 01:12:52 2024 +0000 |
tree | b64cbd6e00cc8d1b26f25edc6c8397a910545d89 | |
parent | 0e96c71c4112c6577fa6a67dd39aa2d47ac52abd [diff] |
roll_util: Remove normalize_remote() This method is now in git_roll_util. Bug: b/359925419 Change-Id: Ib214cc314ad30f086f5da04d0abbb1ad1ebadefc Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/234255 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Reviewed-by: Danielle Kay <danikay@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.