rust-crate-ci

Rust crate CI failures on Windows often stem from path normalization, temp directory short names, or Win32 API return value semantics that behave differently than Linux/macOS. Pre-push validation matching the exact Windows CI job configuration catches these platform-specific correctness issues before pushing code.

Run mandatory ordered commands locally for rustfmt format checks, clippy linting, tests, and release builds. This workflow mirrors the Windows CI job configuration for the swarm-sandbox-runner crate, ensuring format and lint validation passes before committing changes.

Common clippy errors with windows-rs involve API changes, HANDLE thread safety rules, and unused import handling for platform-conditional code. Documented pitfall guidance helps resolve these specific linting failures quickly without debugging failed pipeline runs.

A Windows toolchain is not required locally if you follow exact pre-push validation steps. The provided workflow matches the Windows CI job configuration, resolving platform-specific edge cases like frozen IPC exit codes and NDJSON event contracts remotely.

Fix rustfmt formatting errors in platform-conditional Rust code by addressing unused import handling and following the common pitfall documentation. Matching the exact CI job configuration for format checks prevents these frequent formatting failures from blocking the pipeline.

Windows-only correctness patterns that break Rust crates on CI include path normalization issues, temp directory short name handling, and Win32 API return value semantics. These cause silent failures on Linux/macOS but fail the Windows CI job without specific validation steps.