Add bistable preference-dependent forking scenario #207
Conversation
This file contains 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
Another test for the resolver instability. > This test contains a bistable resolution scenario when not using ahead-of-time > splitting of resolution forks: We meet one of two fork points depending on the > preferences, creating a resolution whose preferences lead us the other fork > point. > > In the first case, we are in cleaver 2 and fork on `sys_platform`, in the > second case, we are in foo 1 or bar 1 amd fork over `os_name`. > > First case: We select cleaver 2, fork on `sys_platform`, we reject cleaver 2 > (missing fork `os_name`), we select cleaver 1 and don't fork on `os_name` in > `fork-if-not-forked`, done. > Second case: We have preference cleaver 1, fork on `os_name` in > `fork-if-not-forked`, we reject cleaver 1, we select cleaver 2, we fork on > `sys_platform`, we accept cleaver 2 since we forked on `os_name`, done. I've also included a tristable system with two iterations lead-up time that is accidentally created. It's not documented, but i wouldn't waste such a cursed scenario.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Another test for the resolver instability.
I've also included a tristable system with two iterations lead-up time that is accidentally created. It's not documented, but i wouldn't waste such a cursed scenario.
With uv 0.2.31: