2bf329cd3b put rescue_window.sh next to rescue_index.sh, and
test_prefix_grouped_files rejects two siblings sharing the `rescue`
prefix (quality-high pass 67). Both move to utils/rescue/ as index.sh and
window.sh, their tests to the mirrored tests/.../utils/rescue/, and every
caller follows: dedicated.sh, the swarm teardown in 00_one.sh, the
workspace workflow, and the swarm and diagnostics READMEs.
The budget-kill drill gave the stand-in a 1 s budget; under the full
parallel unit run the SIGTERM arrived before its EXIT trap was installed,
so nothing was captured and the test failed. The two kill drills now use
KILL_BUDGET = 3 s; their assertions are unchanged. A full `make test-unit`
passes them under load.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diagnostics: recursive container rescue snapshot
container.py is the single failure-diagnostics entry point. The CI
workflows (compose + swarm) call it once on the runner when a job fails;
it captures the current level and then recurses itself through every
Docker-in-Docker boundary, so one call collects evidence from the
outermost runner down to the innermost application container. It always
exits 1.
An optional RESCUE_DEADLINE epoch caps every command on every level; once it
has passed, each remaining capture is written as a
[skipped: past RESCUE_DEADLINE] placeholder. The compose trap in
dedicated.sh sets it through
rescue/window.sh only when
the distro budget's SIGTERM has already arrived.
flowchart TB
subgraph entry["🩺 One workflow call on failure()"]
wf["⚙️ CI step (compose + swarm identical)<br/>INFINITO_RESCUE_DIAGNOSTICS_DIR=/tmp/rescue-diagnostics/<app><br/>python3 utils/diagnostics/container.py <app> <context>"]:::infra
end
subgraph level["📸 Per-level capture (repeated on every depth)"]
direction TB
host["🖥️ Host facts<br/>meta, uname, df/free/uptime,<br/>journal, dmesg OOM evidence"]:::store
dumps["📂 local-dumps/<br/>in-play role evidence from<br/>DIR_RESCUE_DIAGNOSTICS (pg_hba, xwiki)"]:::store
rtc["🐳 Runtime state<br/>info, stats, ps -a,<br/>per-container logs + inspect"]:::store
svc["🐝 Swarm services<br/>ls, per-service ps + logs"]:::store
end
subgraph recursion["🔁 Recursion (RESCUE_MAX_DEPTH, default 3)"]
direction TB
probe["🔍 For every RUNNING container:<br/>has python3 + docker/container runtime?"]:::step
copy["📤 Copy itself in<br/>(stdin → /tmp/rescue-self.py)"]:::step
nested["🩺 Run nested capture<br/>RESCUE_DEPTH+1, own staging dir"]:::step
pull["📥 tar the nested snapshot back to<br/>containers/<name>/nested/ + clean up"]:::step
probe -->|yes| copy --> nested --> pull
probe -.->|no: plain app container,<br/>logs already captured| skipped["⏭️ skip"]:::skip
end
wf --> level --> recursion
nested -.->|same program,<br/>one level deeper| level
result["🗂️ Artifact tree (uploaded by CI)<br/><app>-<stamp>-<pid>/<br/>├── meta/system/journal/…<br/>├── local-dumps/…<br/>├── containers/<name>.log + .inspect.json<br/>├── containers/<did-node>/nested/<app>-…/ (recursion)<br/>└── services/<svc>.log + .ps.txt"]:::store
recursion --> result
classDef infra fill:#f3f7fb,stroke:#d6e2ee,color:#455a64;
classDef store fill:#f1f8f6,stroke:#d5e7e2,color:#455a64;
classDef step fill:#fbf6f0,stroke:#eee1cf,color:#455a64;
classDef skip fill:#f7f8f9,stroke:#e3e6e9,color:#455a64;
style entry fill:#ffffff,stroke:#e6e6e6;
style level fill:#ffffff,stroke:#e6e6e6;
style recursion fill:#ffffff,stroke:#e6e6e6;
Ansible rescue: blocks are forbidden
(tests/lint/ansible/structure/test_no_rescue_blocks.py); the rare
justified block (# nocheck: rescue-<reason>) leaves its role-specific
evidence in DIR_RESCUE_DIAGNOSTICS, which every capture level ships as
local-dumps/.