Files
Chris MeyersandClaude Fable 5.1 7dfb1ecbee Reclaim runner disk before the awx-operator molecule test
The awx-operator job builds the AWX and operator images, loads a second
copy of each into the kind node, then pulls awx-ee, postgres, redis and
ingress-nginx on top - roughly 10G at peak, nearly all of it under
/var/lib/docker. The runner image itself already occupies about 60G
before any of that.

The existing 'Free disk space after Docker build' step prunes the builder
cache, but there is almost nothing there to reclaim: it logs
'Total reclaimed space: 0B' in the runs I checked. Remove the preinstalled
toolchains this job never uses instead, which frees around 20G.
/opt/hostedtoolcache is left in place because setup-python installs there.

Also collect the debug bundle on any failure rather than only on a
timeout, and record df and docker system df in it. A run that dies from a
full disk is not a timeout, so today it produces no artifact at all and
reads like a hang. Reclaim space before creating or writing anything,
since at 0 bytes free the mkdir and redirects would otherwise fail before
any cleanup ran.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RKgCs96cP5LsdUFrBp4wX3
2026-09-03 14:24:45 -04:00
..
2024-08-22 13:48:56 -04:00
2024-08-22 13:48:56 -04:00