Add test case for backjumping when dependencies are not linked #3363
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.
This is another test for the issue described in #3327. The previous test started passing after #3221 was merged. I found this test case with QuickCheck and tried to clean it up, but, unfortunately, it's still messy. The failure only occurs with a specific goal order.
The solver must backtrack to avoid linking 1.D. However, none of the conflict sets at level 6 contain 1.D. 1.D should be added on the line with the message "dependencies not linked".