| commit | e067a5c2cac89f8097e955c908aac968ed71dd43 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@google.com> | Fri Jun 21 20:32:00 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 21 20:32:00 2024 +0000 |
| tree | 329d3f42062d40f4b8fff28b0c1cc6067f8ef8f2 | |
| parent | 5df35ad61b04cc3cebbf5490757ad384d2a70c0b [diff] |
bazel: Fix project name recognition In same cases the name argument for the next git_repository rule is closer than the one for the same git_repository rule. Change the search for adjacent lines to stop when a blank line is encountered to keep this from happening. Example of a failure: http://ci.chromium.org/b/8744560856223940497 Change-Id: I281c8c81265c40ca865d40c5aefa64ade14613ff Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/217030 Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Reviewed-by: Ted Pudlik <tpudlik@google.com> Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-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.