-
Notifications
You must be signed in to change notification settings - Fork 703
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
Flaky tests on AppVeyor #5393
Comments
#4005 is another AppVeyor thing apparently caused by concurrent access to the package database, and fixed in 8.2. Maybe this is related and it would go away if we upgraded AppVeyor's GHC? |
@quasicomputational there's one way to find out, isn't there? :) |
quasicomputational
added a commit
to quasicomputational/cabal
that referenced
this issue
Jun 24, 2018
In the hope that this will solve haskell#5393.
4 tasks
quasicomputational
added a commit
to quasicomputational/cabal
that referenced
this issue
Jun 24, 2018
In the hope that this will solve haskell#5393.
appveyor have been quite reliable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here's a typical example, from #5392:
These failures aren't happening on every attempt; maybe half or a quarter are affected? I've never seen anything like that from Travis, so it looks like it might be Windows-only, or something to do with the specific AppVeyor environment.
The text was updated successfully, but these errors were encountered: