| commit | ce8115d5e032db0d6ecbf290dad59b9e572e1359 | [log] [tgz] |
|---|---|---|
| author | April Kallmeyer <ask@chromium.org> | Wed Dec 17 13:27:33 2025 -0800 |
| committer | Lei Zhang <thestig@chromium.org> | Wed Dec 17 13:27:33 2025 -0800 |
| tree | bedc560916c08f9bc8834f1c7ab23f46d43e1428 | |
| parent | a5ab8986424a5e9e2a307616c728049d2d8d0b44 [diff] |
Add linux no_partition_alloc runners One that's just the base linux config (with agg), the other does xfa and skia to get more coverage. Bug: 469000730 Change-Id: I2d7aca37faf7c5f11f16a461c0ff41ce7bea96d5 Reviewed-on: https://pdfium-review.googlesource.com/c/pdfium/+/139970 Reviewed-by: Tom Sepez <tsepez@chromium.org> Auto-Submit: April Kallmeyer <ask@chromium.org> Commit-Queue: Tom Sepez <tsepez@chromium.org> Commit-Queue: April Kallmeyer <ask@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org>
This directory contains configuration files for chrome-infrastructure services.
For the most part, the actual configs consumed by LUCI live under generated/. Those files are generated by executing the .star files at the root of the repository. Don't edit the generated files directly if the configs need to be changed. Instead, edit the Starlark file and execute it to regenerate the files in generated/ directory.
To manually execute the Starlark code, you will need to have lucicfg in your PATH, and run:
lucicfg generate main.star
Or you can execute the .star file directly:
./main.star