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
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.
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.
In CI we cache
~/.cabal
frommain
and each feature branch begins with a cache of the most recentmain
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:
test/Spec.hs or executables/Main.hs
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):
A.f
inmain
dist-newstyle
directory to to simulate cache storing results of this commits buildA.f
A.f
dist-newstyle
directory from above, simulating cache restore from previous commitweeder --require-hs-files
The text was updated successfully, but these errors were encountered: