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

lint: duplicated id error in case test are duplicated from symlink #3236

Open
bgoncalv opened this issue Sep 24, 2024 · 2 comments
Open

lint: duplicated id error in case test are duplicated from symlink #3236

bgoncalv opened this issue Sep 24, 2024 · 2 comments
Labels
command | lint tmt lint command

Comments

@bgoncalv
Copy link

In case there there is a test with id set and this test is for some reason symlinked as other test, tmt lint will report failure. fail G001 duplicate id

Note, this might not be a bug and the failure would be expected as they are duplicated tests after all, the biggest problem it seems there is no way to have the id set for the test and have tmt lint to not report failure in this case.

Maybe adding an option to disable an specific lint check in the test metadata would be a good solution something like: # tmt-lint: disable=G001

@psss psss added the command | lint tmt lint command label Sep 24, 2024
@psss
Copy link
Collaborator

psss commented Sep 24, 2024

The # tmt-lint comment approach sounds good. We could also consider introducing a global config for the whole fmf tree. The following issue might be slightly related:

There is a proposal to have an .fmf/config file where additional config could be stored for that given fmf tree and would affect the way in which the fmf metadata are gather. We could have a tmt section there or introduce .fmf/tmt or, perhaps, have a .tmt/config file for tmt specific configuration.

@psss
Copy link
Collaborator

psss commented Sep 25, 2024

Note: This might a duplicate of #2048:

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

No branches or pull requests

2 participants