Fix cabal solver dead ends breaking Windows CI - #131
Merged
Conversation
…solver backjump limit
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three upstream bounds problems were making
cabalfail to resolve on Windows.transformers-compat < 0.8—monad-control-1.0.3.1caps it at< 0.8andmonad-loggerneedsmonad-control >= 1.0, so no plan with 0.8 is satisfiable. Windows / GHC 9.10.3 committed to it early and hit the 4000-backjump limit.kubernetes-api -usekatip— every katip release capsWin32 < 2.14, but GHC 9.10/9.12 on Windows shipWin32-2.14.1.0as a boot library. The flag only picks kubernetes-api's internal logging backend; monad-logger was already in the tree and nothing here references katip.max-backjumps: 20000— headroom, since we tripped the default twice on unrelated dead ends.CI: 23/23 green.