ci / test (push) Successful in 10s
ci / patches-apply (push) Successful in 25s
ci / quality (push) Successful in 36s
ci / badges (push) Skipped
ci / kernel-symbols (push) Successful in 4m38s
ci / mcdc (push) Successful in 37s
ci / bench (push) Successful in 6s
ci / qemu-tools (push) Failing after 15s
ci / prune-artifacts (push) Skipped
ci / kernel-build (push) Skipped
ci / test (pull_request) Successful in 9s
ci / prune-artifacts (pull_request) Skipped
ci / mcdc (pull_request) Successful in 34s
ci / bench (pull_request) Successful in 20s
ci / kernel-build (pull_request) Skipped
ci / qemu-tools (pull_request) Failing after 57s
ci / patches-apply (pull_request) Successful in 1m16s
ci / kernel-symbols (pull_request) Successful in 2m14s
ci / badges (pull_request) Skipped
ci / quality (pull_request) Successful in 2m51s
run.sh --agent SOCK adds a third pci-serial after ctl and rs485 (their ttyS order is unchanged) and warden.agent on the command line. Stage-2 init then runs warden_agent (rootfs/etc/warden-lib.sh) on that port with echo off: `@run ID SECS B64` runs a script and answers <<BEGIN ID>>, the base64 of its output and <<END ID RC>>; `@chunk` pieces get past the 4095-byte cooked line; a script past its deadline is killed with its process group and answers 124 (the panel BusyBox has no timeout). It is the guest channel of flare-edge tools/soak/rig-qemu.py, which needs bus reads and writes, the clock and /proc inside the gate image. Rig rootfs only: no panel image carries it. Tests: qemu/tests/agent-test.sh (sh and busybox sh, in CI) and new run-sh-args-test.sh cases (agent last, warden.agent only with the flag). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BdKQBQkJkq4zE7iPFMkAhS