Chris Tate 7cdfe16c9b Cap the Linux test step's memory and spread memory-heavy side files ...

The Linux test shards run their suites in a transient systemd scope with
MemoryMax=13G and no swap, below the runner's 16 GB. A process tree that
grows past the cap loses its largest process to the kernel, and the job
log names the failing test, where the runner itself ran out of memory
and left no log. Hosts without systemd run the suites directly.

The side-queue balancer also takes a table of memory-heavy files, with
their measured peak. They run whole in the cost-balanced task, and each
goes to the shard with the least memory-heavy work so far, after the
time-balanced files. decl-boundary.test.ts, which peaks at about 1.8 GB
alone and had no time measurement, so vitest's file sharding put it in
shard 11, is the first entry. It now runs in shard 1 (plain) and 6 (san).

2026-10-23 14:24:38 -05:00

..

actions

Fix Android API 26 runtime release builds (#614)

2026-10-02 02:29:24 -05:00

workflows

Cap the Linux test step's memory and spread memory-heavy side files

2026-10-23 14:24:38 -05:00

STACKED_CI.md

Harden stacked CI scope and merge validation (#771)

2026-10-08 14:57:21 -05:00