-
Notifications
You must be signed in to change notification settings - Fork 704
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
Solver runs out of backjumps (network-3.0 not allowed). #5882
Comments
The last time the max-backjumps was increased was back in 2014 (see 0229cd5) as suggested per haskell#1780, and while `--reorder-goals` might often help as well, it also often comes at a bigger runtime penalty on average than doubling the max-backjumps. This should also address issues such as haskell#5882
I'm not sure I can reproduce the issue. I couldn't find the commit 6b533515ccf1f16dd29b4c2dfc1daec2cbe07d70 in servant-ekg. EDIT: I just noticed that max-backjumps in 2000 in the logs. |
@grayjay the cucrrent master fails if you remove |
unless the trustees somehow already fixed it we're hitting backjump constraints due to the new network on a straight |
@phadej Thanks, I can reproduce the issue on master now with
|
Note that trustee fixes mean that the current index state seems to no longer trigger the backjumps issue, which is great news (though of course we should get this fixed anyway, since who knows when we'll hit it again) |
@gbaz I suspect it's not due trustee fixes, but due more packages accepting |
lambdabot/lambdabot#183 seems related. In this case the problem is ultimately caused by a major version bump of |
This issue should be fixed by #5918. |
haskell-servant/servant-ekg#7
6b533515ccf1f16dd29b4c2dfc1daec2cbe07d70
fromservant-ekg
cabal-install
version2.5+git20190112.1.6a24235-6~18.04
cabal v2-update 'hackage.haskell.org,2019-02-05T16:11:01Z
however
--reorder-goals
plan is found.with reorder-goals
This works
Expand
without reorder goals
this doesn't
expand (the log is truncated, but it's visible where backjumps are spent)
cc @grayjay
The text was updated successfully, but these errors were encountered: