You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: