run-on-arch-action tested by Argusic Runner

What the test found

npm install succeeds and the action's full code path runs end-to-end under a docker shim (install script executed, container run executed, env/volumes/outputs all flowed), because no real docker/QEMU exists in this container.

GitHub Action for cross-arch docker runs; has no unit tests. npm install exited 0 (7 packages, 3 moderate audit warnings). Node 18.19.1, Ubuntu 24.04, no docker/podman/qemu/root in container, so verification is a faithful host-side mock: docker run/build/binfmt/sudo emulated by shim at /tmp/runonarch-shims, with the action's real scripts executing. The docker build stage ran the install script (printed install-ran-ok), the emulated run stage executed the generated commands script (uname -m printed x86_64) with env and volumes passed, and host setup wrote host_shell_options=ehuB to GITHUB_OUTPUT. Files produced by the action and test artifacts were moved out of the repo; only package-lock.json differs (lockfile v3 from the fresh npm install).

Argusic installed run-on-arch-action in 2 minutes and launched it; verification reached Verified with mock services. 3 of 3 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of run-on-arch-action

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.