commit | d2a98aae6949f0644b829fceec90f90555e45fe9 | [log] [tgz] |
---|---|---|
author | Rob Mohr <mohrr@google.com> | Thu Jan 30 10:31:20 2025 -0800 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 30 10:31:20 2025 -0800 |
tree | 40f963b6d2da07afb5f30e44b54e927243c2d9ba | |
parent | 68d80b85b8b764f9be3a0e5179582a778fa42963 [diff] |
Revert "submodule_roll: Also update MODULE.bazel.lock" This reverts commit 68d80b85b8b764f9be3a0e5179582a778fa42963. Reason for revert: causing failures like http://ci.chromium.org/b/8724294241434625137 Original change's description: > submodule_roll: Also update MODULE.bazel.lock > > Bug: b/393158553 > Change-Id: Ibc714e260615462f9d21b4e5d507a49ee96e8e7c > Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/263592 > Reviewed-by: Austin Foxley <afoxley@google.com> > Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> > Commit-Queue: Rob Mohr <mohrr@google.com> > Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> TBR=mohrr@google.com,pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com,afoxley@google.com,tpudlik@google.com,android-build-ayeaye@system.gserviceaccount.com Change-Id: I823b1280c7a3cce31321a7f9d16ab0d4e6da713f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: b/393158553 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/263634 Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Reviewed-by: Austin Foxley <afoxley@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.