Summary
The checks-windows CI job is consistently failing on PRs and on main due to a path-handling test failure in path-safety. The test expects Unix-style paths (~/file.txt) but runs on a Windows runner where paths use backslashes.
Reproduction
This failure is visible on multiple recent PRs and on main itself:
Error
1 failed | 705 passed | 3 skipped (709)
1 failed | 5764 passed | 20 skipped (5785)
The single failing test is in the path-safety module, where expect(result).toBe(${fakeHome}/file.txt) fails because Windows uses backslash paths.
Expected behavior
Windows CI tests should pass, or the path-safety test should account for platform-specific path separators.
Summary
The
checks-windowsCI job is consistently failing on PRs and onmaindue to a path-handling test failure inpath-safety. The test expects Unix-style paths (~/file.txt) but runs on a Windows runner where paths use backslashes.Reproduction
This failure is visible on multiple recent PRs and on
mainitself:checks-windowsfailsmainbranch CI runs also show repeated failuresError
The single failing test is in the path-safety module, where
expect(result).toBe(${fakeHome}/file.txt)fails because Windows uses backslash paths.Expected behavior
Windows CI tests should pass, or the path-safety test should account for platform-specific path separators.