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

Directive: mark-non-leaf #231

Open
LecrisUT opened this issue Apr 16, 2024 · 0 comments
Open

Directive: mark-non-leaf #231

LecrisUT opened this issue Apr 16, 2024 · 0 comments

Comments

@LecrisUT
Copy link

#223 is introducing mark-leaf as a mechanism to make a directory fmf file into a leaf, e.g. with /root/leaf_test (e.g. from /root/leaf_test.fmf) it allows /root to also be a valid test. This proposal is to also support the opposite, i.e. if we have a file /root.fmf do not expand it as a leaf.

This is relevant when we consider graft mechanism in #99, and specifically when one of the trees is virtual (generated from discover step). E.g. if the generated tree is like /root/leaf_test_A, /root/leaf_test_B, we could have a /root.fmf file such that it is inherited in all leaf_test_*. The issue is that currently /root would be considered as a leaf, and can affect tmt lint or define dummy tests for other discover steps. Having this mechanism will effectively hide the /root base, until it is expanded by leaves (through graft mechanism).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant