bazel_roll: Better handle trimming around rules

The code for extracting the center of a match used to trim a bunch of
lines from the end, then recalculate the center and trim a bunch of
stuff from the beginning. If many lines were removed from the end, then
the updated center could be on a different rule and the parsing would
fail.

Change-Id: I8eda8e7004a3ae28c048c0687177c0448b8dce38
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/424032
7 files changed
tree: 0d155b4677534e350765efcdcd4a99b06fabc84c
  1. infra/
  2. recipe_modules/
  3. recipe_proto/
  4. recipes/
  5. scripts/
  6. .aiderignore
  7. .editorconfig
  8. .gitignore
  9. .style.yapf
  10. AUTHORS
  11. GEMINI.md
  12. LICENSE
  13. OWNERS
  14. presubmit.sh
  15. pyproject.toml
  16. README.md
  17. recipes.py
  18. shac.ensure
  19. shac.star
  20. shac.textproto
README.md

Pigweed Recipes

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.

Getting the Code

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

Running Tests

./presubmit.sh runs three different sets of tests:

  • Recipe expectation tests (./recipes.py test train)
  • Formatting (./black --diff --check .)
  • Dependencies (.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.