kevinveenbirkenbachandClaude Opus 4.8 c2e06b9056 fix(ci): capture rescue diagnostics inside the DiD container before teardown ...

In compose/host mode the whole nested app stack lives inside INFINITO_CONTAINER, which dedicated.sh's EXIT-trap cleanup removes. The separate workflow-level rescue step ran container.py on the runner AFTER that teardown, so it saw an emptied Docker and captured only 12 host files (unlike swarm, whose DiD nodes outlive the deploy step and get recursed into).

Run the recursive container.py capture inside INFINITO_CONTAINER during cleanup, before the existing copy-out and the teardown, so it descends into the app containers. Drop the now-redundant, post-teardown 'Collect rescue diagnostics' step from the compose and host workflows (runner state stays covered by dump_state.sh; the upload step keeps uploading what dedicated.sh writes). container.py is now called once per mode: inside dedicated.sh for compose/host, at runner level for swarm.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-16 03:44:17 +02:00

..

act

refactor(swarm-tests): move teardown and topology under utils, drop shell rescue collector

2026-07-12 03:15:53 +02:00

ci

fix(ci): capture rescue diagnostics inside the DiD container before teardown

2026-07-16 03:44:17 +02:00

local

refactor: single /var/lib SPOT + swarm Playwright artifact upload

2026-06-26 17:01:09 +02:00

swarm

fix(dr-drill): drill node-local workloads instead of skipping them

2026-07-15 16:07:39 +02:00

roundtrip.sh

test(lint): forbid absolute-path shell defaults outside a SPOT

2026-07-12 03:15:52 +02:00