-
Notifications
You must be signed in to change notification settings - Fork 520
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
Paket deadlock since 0.38.0? #746
Comments
yes please try to send a fix. we should cancel the license download after one or two seconds it's just not important enough. |
is 6d2f239 ready? |
nope still testing |
It looks like everything times out now with 5 secs on the async and 3 secs on the request. |
But at least it doesn't fail anymore: See #747. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Paket pretty much always deadlocks since 0.38.
The issue pops up as soon as you delete the cache and are on linux.
Repro:
The last message seems to be different depending on the mono tracing flags. However is seems to be always near the FSharp.Compiler.Service License, after 2 previous 404 warnings.
I tried out the last few versions of Paket until the build started working again, see here: https://travis-ci.org/matthid/Yaaf.Shell/builds. I can repro this on my local gentoo machine as well.
Windows is not hit, as you can see here: https://ci.appveyor.com/project/matthid/yaaf-shell/history
Note it is also possible that the default timeout is >10 minutes (or longer on mono) and that's the reason why travis kills the process (I did not try to wait a day to see if it eventually finishes..)
Or this could be some mono race condition bug we should IMHO work around somehow, if possible.
That said: Can somebody reproduce this? Should I try to send a fix for this?
The text was updated successfully, but these errors were encountered: