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
Creating this issue because I am disabling this particular travis test as it is not informative about the health of a particular build of stack, and I have no idea what to do about the issue.
It fails with many errors about missing files in packages. These errors continue to stick around due to travis caching, so I cleared out the cache. After that, I get different errors:
/home/travis/.ghc/x86_64-linux-7.10.2/package.conf.d/package.cache: openBinaryFile: does not exist (No such file or directory)
Despite our travis not changing, the output in the first two builds seems to be coming from a different version of cabal than the newest build. Perhaps it has something to do with Dependency Cabal ==1.22.7.0: using Cabal-1.22.7.0?
The text was updated successfully, but these errors were encountered:
Creating this issue because I am disabling this particular travis test as it is not informative about the health of a particular build of stack, and I have no idea what to do about the issue.
This is the last successful build: https://travis-ci.org/commercialhaskell/stack/jobs/128446008
The first one that failed: https://travis-ci.org/commercialhaskell/stack/jobs/129048856
It fails with many errors about missing files in packages. These errors continue to stick around due to travis caching, so I cleared out the cache. After that, I get different errors:
/home/travis/.ghc/x86_64-linux-7.10.2/package.conf.d/package.cache: openBinaryFile: does not exist (No such file or directory)
Despite our travis not changing, the output in the first two builds seems to be coming from a different version of cabal than the newest build. Perhaps it has something to do with
Dependency Cabal ==1.22.7.0: using Cabal-1.22.7.0
?The text was updated successfully, but these errors were encountered: