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.

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

scenarios: add basic test for testing marker disjointness #182

Merged
merged 1 commit into from
Jun 7, 2024
Merged
Changes from all commits
Commits
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
29 changes: 29 additions & 0 deletions scenarios/fork/marker-disjoint.toml
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
name = "fork-marker-disjoint"
description = '''
A basic test that ensures, at least in this one basic case, that forking in
universal resolution happens only when the corresponding marker expressions are
completely disjoint. Here, we provide two completely incompatible dependency
specifications with equivalent markers. Thus, they are trivially not disjoint,
and resolution should fail.

NOTE: This acts a regression test for the initial version of universal
resolution that would fork whenever a package was repeated in the list of
dependency specifications. So previously, this would produce a resolution with
both `1.0.0` and `2.0.0` of `a`. But of course, the correct behavior is to fail
resolving.
'''

[resolver_options]
universal = true

[expected]
satisfiable = false

[root]
requires = [
"a>=2 ; sys_platform == 'linux'",
"a<2 ; sys_platform == 'linux'",
]

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