You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3. Consider adding `--force` flag to binstall to ensure fresh install to correct location
75
76
4. Add `which cargo-tarpaulin` and `echo $PATH` debug steps to CI workflow
76
77
<!-- SECTION:NOTES:END -->
78
+
79
+
## Final Summary
80
+
81
+
<!-- SECTION:FINAL_SUMMARY:BEGIN -->
82
+
## Fix
83
+
84
+
Added `--force` flag to `cargo binstall` in `.github/workflows/test.yml` so tarpaulin is always installed to `~/.cargo/bin/` regardless of stale metadata.
85
+
86
+
## Root Cause
87
+
88
+
`~/.cargo/.crates.toml` on the Mac Mini runner had metadata from a previous `cargo install cargo-tarpaulin` (installed via mise to `~/.local/share/mise/shims/`). Binstall found the metadata, reported "already installed", and skipped — but the binary wasn't in `~/.cargo/bin/` where `cargo tarpaulin` looks.
89
+
90
+
## Verification
91
+
92
+
- Force-installed tarpaulin on Mini via SSH, confirmed binary at `~/.cargo/bin/cargo-tarpaulin`
93
+
- CI run [23319951069] passed all 4 jobs end-to-end (Build & Rust Tests, Playwright E2E, Vitest, Lint)
0 commit comments