Skip to content

Spurious failures due to intermittent stack concurrency bug

We have spurious failures because of https://github.com/commercialhaskell/stack/issues/6388.

What's not clear to me is why a package that required a call to updateHackageIndex in one run did not require the call in a different run. I would expect the set of packages that trigger the call to be fixed. Are we caching the Pantry database?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information