Google Git
Sign in
pigweed / infra / recipes / 67d58770e41851a1353eded19a2db6fdfa97d143
commit67d58770e41851a1353eded19a2db6fdfa97d143[log] [tgz]
authorRob Mohr <mohrr@google.com>Fri Aug 09 14:05:39 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Aug 09 14:05:39 2024 +0000
tree7e353d930b6ba0f2556eac70d6cd6cf8496af13a
parent37cdb4e744ecb4c3766f88aa57d7571ee1e0d9d4 [diff]
checkout: Don't use cache when patching WORKSPACEs

Don't use the git cache when patching WORKSPACE or MODULE.bazel files.
The extra logic for handling caches seems to be causing problems.

Example of failure:

* http://ci.chromium.org/b/8740118115170705313

Tested with led:

* http://ci.chromium.org/b/8740117292319035601
* http://ci.chromium.org/b/8740117286618230449
* http://ci.chromium.org/b/8740117280860990449

Bug: b/358442949
Change-Id: I122b3d8a0cdbaa8643d3aca1b8b782aeb2bf5a67
Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/228555
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Reviewed-by: Oliver Newman <olivernewman@google.com>
Commit-Queue: Auto-Submit <auto-submit@pigweed-service-accounts.iam.gserviceaccount.com>
2 files changed
tree: 7e353d930b6ba0f2556eac70d6cd6cf8496af13a
  1. infra/
  2. recipe_modules/
  3. recipes/
  4. scripts/
  5. black ⇨ .cipd/black
  6. .editorconfig
  7. .gitignore
  8. .style.yapf
  9. AUTHORS
  10. cipd.ensure
  11. LICENSE
  12. OWNERS
  13. presubmit.sh
  14. pyproject.toml
  15. README.md
  16. recipes.py
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.