| commit | 90f5d95844aaa55d49739cf805f75b935fac9d4b | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@google.com> | Wed Oct 09 19:09:10 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 09 19:09:10 2024 +0000 |
| tree | f93e1984dfdc6e19d2d06a30f8ceb97eddbc5358 | |
| parent | af2d1e4e69ab57450d60130102795db2ee369b94 [diff] |
bazel: Don't download any outputs This should speed up CI and CQ builds by not requiring Bazel to actually download any remotely cached artifacts, unless they're required for another builds action. This should have a substantial impact on runtime: looking at profiles like https://ui.perfetto.dev/#!/?s=b8194b3e6f9a88bf2f3036b89d3082e382cfd2e3, it seems like much of the time is spent downloading these outputs. Many of them we we don't use for anything: all we're doing here is verifying that they _can_ be successfully built! Change-Id: I04d6a8f96a16fadf1976a579b48a1a569fbc9791 Reviewed-on: https://pigweed-review.googlesource.com/c/infra/recipes/+/238614 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Rob Mohr <mohrr@google.com> Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Rob Mohr <mohrr@google.com> Commit-Queue: Ted Pudlik <tpudlik@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.