Skip to content

fix(ci): unbreak Signal Chain CI (fmt, clippy, windows shell) - #4

Merged
SuperInstance merged 1 commit into
mainfrom
fix/signal-chain-ci-fmt-clippy-windows
Sep 21, 2026
Merged

SuperInstance merged 1 commit into
mainfrom
fix/signal-chain-ci-fmt-clippy-windows

Conversation

@SuperInstance

Copy link
Copy Markdown
Owner

Root causes (Signal Chain CI red on main since 2026-08-31, run 33355653703)

  1. cargo fmt jobopenshell-signal-chain wasn't rustfmt-clean (mostly multi-line call-argument wrapping). Fixed by running cargo fmt -p openshell-signal-chain; no logic changes.
  2. test-ubuntu / test-macoscargo clippy failed with 'cargo-clippy' is not installed for the toolchain '1.95.0-...'. The Configure Rust step never installs the clippy component. Added rustup component add clippy.
  3. test-windows — the Configure Rust step's rustup target add ... 2>/dev/null || true uses bash-style redirection but ran under the Windows runner's default shell (pwsh), which tried to resolve /dev/null as a literal path (Could not find a part of the path 'D:\dev\null') and failed the whole step before any test ran. Added shell: bash so the step behaves the same on all three OSes.

Verification

Ran locally against the same crate/toolchain:

cargo fmt -p openshell-signal-chain -- --check   # now passes
cargo test -p openshell-signal-chain             # 51 passed
cargo clippy -p openshell-signal-chain -- -D warnings   # clean, once clippy component installed

The build-arm64 job (cargo check only, no clippy) was already green and is untouched.

Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01JV2C8fnD86DNwXoyHPd7X9


Generated by Claude Code

Three independent root causes for the red main CI in Signal Chain CI:

- `cargo fmt` job: openshell-signal-chain wasn't rustfmt-clean. Ran
  `cargo fmt -p openshell-signal-chain` (formatting only, no logic change).
- test-ubuntu/test-macos: `cargo clippy` failed with "'cargo-clippy' is
  not installed for the toolchain" because the "Configure Rust" step
  never installs the clippy component. Added `rustup component add
  clippy`.
- test-windows: the "Configure Rust" step uses bash-style `2>/dev/null`
  redirection but runs under the runner's default shell on Windows
  (pwsh), which tried to resolve /dev/null as a literal path and failed
  immediately. Added `shell: bash` so the step runs consistently across
  all three OSes.

Verified locally: `cargo fmt -p openshell-signal-chain -- --check`,
`cargo test -p openshell-signal-chain`, and `cargo clippy -p
openshell-signal-chain -- -D warnings` all pass.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JV2C8fnD86DNwXoyHPd7X9
@SuperInstance
SuperInstance merged commit ce03632 into main Sep 21, 2026
14 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants