Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add failing incomplete markers scenarios #200

Merged
merged 2 commits into from
Jul 9, 2024
Merged

Add failing incomplete markers scenarios #200

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2bc775e
Add failing incomplete markers scenarios
konstin Jul 9, 2024
add2be1
Explain test goal
konstin Jul 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions scenarios/fork/incomplete-markers.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
name = "fork-incomplete-markers"
description = '''
The root cause the resolver to fork over `a`, but the markers on the variant
of `a` don't cover the entire marker space, they are missing Python 3.10.
Later, we have a dependency this very hole, which we still need to select,
instead of having two forks around but without Python 3.10 and omitting
`c` from the solution.
'''

[resolver_options]
universal = true

[expected]
satisfiable = true

[root]
requires = [
"a==1; python_version < '3.10'",
"a==2; python_version >= '3.11'",
"b",
]

[packages.a.versions."1.0.0"]
[packages.a.versions."2.0.0"]

[packages.b.versions."1.0.0"]
requires = [
"c; python_version == '3.10'",
]

[packages.c.versions."1.0.0"]