[aw-failures] smoke-crush: EROFS on npm global install to read-only hostedtoolcache

[github-actions]

Smoke Crush fails immediately at the Crush CLI install step because npm install -g @charmland/crush`` tries to write into /opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/, which is read-only on GitHub-hosted runners.

Affected Runs

• §24911755864 — Smoke Crush (issue [aw] Smoke Crush failed #28344, pre-agent failure)

Root Cause

EROFS: read-only file system,
mkdir '/opt/hostedtoolcache/node/24.14.1/x64/lib/node_modules/`@charmland/crush`/bin'

/opt/hostedtoolcache is managed by the setup-node action and is read-only after tool setup. A npm install -g without a custom prefix attempts to write into this path, which is locked.

Proposed Remediation

Change the Crush install step to use a writable prefix, e.g.:

- name: Install crush
  run: |
    npm install --prefix "$HOME/.crush" `@charmland/crush`
    echo "$HOME/.crush/bin" >> $GITHUB_PATH

Or use a local install (npm install @charmland/crush``) and invoke via npx.

Success Criteria

• Smoke Crush installs the Crush CLI without EROFS error
• Crush agent runs to completion and produces expected smoke output
  Related to [aw-failures] [aw] Failure Investigator (6h) - Issue Group #28268

Generated by [aw] Failure Investigator (6h) · ● 274.8K · ◷

• expires on May 2, 2026, 1:20 AM UTC