fix(ci): isolate Windows Tauri test harness

- keep Windows executable checks on targets that run on the hosted image
- compile Tauri-backed queue and library tests without executing the broken harness
- share root-scoped canonical cache logic with the Windows safety regression
This commit is contained in:
NimBold
2026-08-19 13:03:07 +03:30
parent dd04ed40d6
commit 6be0f5ca5a
4 changed files with 123 additions and 41 deletions
+4 -5
View File
@@ -51,8 +51,7 @@ npm run smoke:torrent:failure-paths
```
Native CI runs this failure-path smoke after staging the target-specific
bundled engines on macOS, Windows, and Linux. Windows runs the queue-manager
and Torrent RPC integration targets explicitly, plus atomic-storage,
canonical-cache, and web-seed normalization targets; the general Rust job
compiles the library tests without executing the known-broken Tauri library
harness.
bundled engines on macOS, Windows, and Linux. Windows executes the Torrent RPC,
atomic-storage, canonical-cache, and web-seed normalization targets, while
compiling (but not executing) the queue-manager and library test binaries;
the Tauri mock harness exits before running on the Windows runner.