Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stale hie files make weeder reporting inaccurate in certain renaming situations #113

Open
codygman opened this issue Mar 13, 2023 · 0 comments

Comments

@codygman
Copy link

In CI we cache ~/.cabal from main and each feature branch begins with a cache of the most recent main build. Then each successive CI build caches to a key with the feature branch name.

We also use require-hs-files

I either have a bug from:

EDIT: Our module name's don't mention module namespace. What's weird is we had no issues until the improved recompliation avoidance in ghc 9.4 that IIRC uses timestamps.

If it's the last one, it might be fixed by re-implementing #82 with HieDB.Query.getUnreachable)

Otherwise to the best of my memory, here's the series of events that seems to lead to this (haven't reproduced yet, but these steps might):

  • build project calling a function A.f in main
  • copy the dist-newstyle directory to to simulate cache storing results of this commits build
  • create a weed by removing reference to A.f
  • remove A.f
  • restore the dist-newstyle directory from above, simulating cache restore from previous commit
  • build project
  • run weeder --require-hs-files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant