Summary
The Ubuntu Build and Test job for #1411 intermittently failed in litebox_runner_linux_userland::run::test_static_exec_with_rewriter because the runner closed the active broker association. The unchanged commit passed local reproductions and a rerun of the same workflow, suggesting a runner/broker association teardown race rather than a deterministic regression.
Failure evidence
The failure surfaced during different inner C programs across retries. The first attempt reached thread_exit_exec_rewriter; later attempts failed around execve_exec_rewriter. During an exec retry, the guest printed:
[OK] exec caller became leader; cloexec fd 3 closed; keep fd 4 open
The broker command nevertheless exited with status 1 afterward, which points toward association shutdown/teardown rather than the guest validation itself.
Reproduction attempts
The failure did not reproduce locally on the same commit:
cargo nextest run -p litebox_runner_linux_userland --test run test_static_exec_with_rewriter --no-fail-fast
PASS in 24.317s
cargo nextest run -p litebox_runner_linux_userland --test run --no-fail-fast
15/15 passed; affected test passed in 12.993s
cargo nextest run --no-fail-fast
977/977 passed; affected test passed in 13.353s
Successful unchanged rerun
The failed GitHub Actions job was rerun without any code changes:
We should track the runner/broker association teardown path and improve diagnostics so a future occurrence identifies which side closes the channel and why.
Summary
The Ubuntu
Build and Testjob for #1411 intermittently failed inlitebox_runner_linux_userland::run::test_static_exec_with_rewriterbecause the runner closed the active broker association. The unchanged commit passed local reproductions and a rerun of the same workflow, suggesting a runner/broker association teardown race rather than a deterministic regression.Failure evidence
c59bb54c1c82addc48a8a9b32c3a9871a35bab54ubuntu-latestRun ./.github/tools/github_actions_run_cargo nextest977 tests run: 976 passed, 1 failed, 22 skippedlitebox_runner_linux_userland::run::test_static_exec_with_rewriterBrokenPipe: runner closed the active broker associationThe failure surfaced during different inner C programs across retries. The first attempt reached
thread_exit_exec_rewriter; later attempts failed aroundexecve_exec_rewriter. During an exec retry, the guest printed:The broker command nevertheless exited with status 1 afterward, which points toward association shutdown/teardown rather than the guest validation itself.
Reproduction attempts
The failure did not reproduce locally on the same commit:
Successful unchanged rerun
The failed GitHub Actions job was rerun without any code changes:
c59bb54c1c82addc48a8a9b32c3a9871a35bab54We should track the runner/broker association teardown path and improve diagnostics so a future occurrence identifies which side closes the channel and why.