Alex Goodman eb58f698bd Fix oom when running unit tests in CI (#5284) ...

* fix oom when testing

Signed-off-by: Alex Goodman <wagoodman@users.noreply.github.com>

* right-size CI test runners

the `r` family and `ram=32+128` were sized for the tmpfs footprint rather
than the workload. with the caches back on disk the build+test peak fits in
16GB, so move to `m`/`c` at `ram=16+32`.

- ~27% cheaper per instance-hour on spot, and a much deeper pool to schedule
  against (~20 x86 types vs 7)
- `cpu=4+8` with `ram=16+32` lets price-capacity-optimized opportunistically
  land an 8 vCPU box when it's cheap
- plain `volume=100gb` replaces the provisioned throughput. a 4 vCPU instance
  caps near 150MB/s of EBS and gp3's free baseline is already 125MB/s, so the
  override bought nothing

Signed-off-by: Alex Goodman <wagoodman@users.noreply.github.com>

---------

Signed-off-by: Alex Goodman <wagoodman@users.noreply.github.com>

2026-09-11 14:58:30 -04:00

..

codeql.yaml

chore(deps): bump anchore/workflows/.github/workflows/codeql.yaml (#5032)

2026-07-03 13:26:04 +00:00

release.yaml

chore(deps): bump anchore/sbom-action from 0.24.0 to 0.24.2 (#5250)

2026-09-04 13:29:14 +00:00

validate-github-actions.yaml

chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 (#5270)

2026-09-11 13:53:48 +00:00

validations.yaml

Fix oom when running unit tests in CI (#5284)

2026-09-11 14:58:30 -04:00