Summary
Self-hosted rust-cpu runners (pulseengine-ci-01-{5,6,7,9,10,11,12}) lack unzip, which oven-sh/setup-bun requires to extract the bun binary. This blocks anthropics/claude-code-action from running, which in turn blocks meld's mythos-auto.yml (#162) from completing its scan matrix.
Observed
PR #163 (first end-to-end run): scan job ran with the runner attempting setup-bun → fail at Unable to locate executable file: unzip → action's bun-based entrypoints exit 127 → placeholder-FINDING fallback fires → workflow fails.
PR #166 (second attempt, after mythos-auto.yml plumbing fix in #164): same unzip error, same cascade. My in-workflow apt-get install -y unzip attempt also fails (probably apt-get update issue or sudo perms — exit code 1).
Concrete log snippet:
##[error]Error: Unable to locate executable file: unzip. Please verify either the file path exists ...
/var/lib/runners/runner5/_work/_temp/.../d9f8a6f8.sh: line 3: bun: command not found
##[error]Process completed with exit code 127.
Impact
The mythos-auto.yml workflow (the AI-driven Mythos discover-protocol auto-runner shipped in #162) cannot complete its matrix scan until unzip is available on rust-cpu runners. Every Tier-5 PR by avrabe will trigger this failure cascade.
Asks
- Install
unzip in the rust-cpu runner image (or via post-provisioning script). It's a 200KB Debian package; cost is trivial.
- Alternative: provide a pre-installed bun binary at a known path so workflows can pass
path_to_bun_executable to claude-code-action and skip setup-bun entirely.
Workaround for now
mythos-auto.yml falls back to a FINDING placeholder when structured output is empty; PR-time mythos-pass-done label must be applied manually until this is resolved. The label-only mythos-gate.yml (#151) is unaffected — that gate just checks for the label.
References
Summary
Self-hosted rust-cpu runners (
pulseengine-ci-01-{5,6,7,9,10,11,12}) lackunzip, whichoven-sh/setup-bunrequires to extract the bun binary. This blocksanthropics/claude-code-actionfrom running, which in turn blocks meld'smythos-auto.yml(#162) from completing its scan matrix.Observed
PR #163 (first end-to-end run): scan job ran with the runner attempting
setup-bun→ fail atUnable to locate executable file: unzip→ action's bun-based entrypoints exit 127 → placeholder-FINDING fallback fires → workflow fails.PR #166 (second attempt, after
mythos-auto.ymlplumbing fix in #164): sameunziperror, same cascade. My in-workflowapt-get install -y unzipattempt also fails (probablyapt-get updateissue or sudo perms — exit code 1).Concrete log snippet:
Impact
The
mythos-auto.ymlworkflow (the AI-driven Mythos discover-protocol auto-runner shipped in #162) cannot complete its matrix scan untilunzipis available on rust-cpu runners. Every Tier-5 PR byavrabewill trigger this failure cascade.Asks
unzipin the rust-cpu runner image (or via post-provisioning script). It's a 200KB Debian package; cost is trivial.path_to_bun_executabletoclaude-code-actionand skipsetup-bunentirely.Workaround for now
mythos-auto.ymlfalls back to a FINDING placeholder when structured output is empty; PR-timemythos-pass-donelabel must be applied manually until this is resolved. The label-onlymythos-gate.yml(#151) is unaffected — that gate just checks for the label.References
mythos-auto.ymlintroduction)mythos-auto.ymlplumbing fixes; tried in-workflowapt-get install unzipbut the install step itself exits 1)