mirror of
https://github.com/kuhyx/utils.git
synced 2026-11-10 21:07:15 +01:00
Krzysztof kuhy Rudnicki
8bb4d3a60d
Testing boot_recovery produced a guest that cannot boot: boot-repair read /boot/vmlinuz-linux and initramfs-linux.img on this BIOS/GRUB guest as "orphaned kernel files shadowing the ESP" and deleted them, leaving the sandbox at a GRUB prompt. That is a legitimate sandbox outcome -- destroying the guest is what the tool is for -- but vmbox handled it by hanging. Two independent unbounded waits, both fixed: - vm_wait_ssh counted only its `sleep 2` calls, ignoring the up-to-5s ConnectTimeout each failed probe spends inside ssh. A nominal 150s wait ran past 400s (measured, then cut short by the harness). It now works to a wall clock deadline: the same guest is now reported unreachable in 156s. - _run_recover_rc reboots the stopped guest to read the recorded exit code, and fell through to an unbounded serial console read: 180s for a prompt that never comes plus 300s for a command that never runs, all AFTER the verdict had already been printed. Recovery is best-effort by definition, so both bounds are now short (60s/30s) and overridable. serial_exec's timeouts become env-overridable to make that possible. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VdyMBGCrGVGDWtJ9xe48f3 |
||
|---|---|---|
| .. | ||
| base.sh | ||
| common.sh | ||
| launch.sh | ||
| overlay.sh | ||
| qmp.py | ||
| recorder.py | ||
| repo.sh | ||
| run.sh | ||
| screenshot.sh | ||
| seed.sh | ||
| serial_exec.py | ||
| smoke.sh | ||
| ssh.sh | ||
| verdict.sh | ||