Remote caching is broken on Windows
Nobody has claimed this yet.
- Dominant language
- Starlark
- Stars
- 279
- Forks
- 93
- Avg merge
- 13d 11h
- Merged PRs (30d)
- 3
Description
Using rules_haskell with remote caching enabled is broken on Windows. Absolute paths to package databases find their way into the output of build actions, which leads to build failures when those are re-used on another machine when paths don't match.
This is likely due to lack of sandboxing and/or the various hacks we have put in place to work around the limitations of the Windows file system.
As a side remark: we currently don't test cache behavior on CI. Is this something we would want to put in place ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing a Windows build with rules_haskell and remote caching enabled, then inspect cached action outputs for absolute package-database paths; done means cached outputs can be reused across machines with different paths, with cache behavior covered by CI if that scope is retained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100