-
Notifications
You must be signed in to change notification settings - Fork 345
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
Hardcoded nrunner removal in TestSuite #5955
Conversation
This is a removal of left over of legacy code. When avocado supported `legacy` and `nrunner` runners we also distinguished between resolver resolution and test load. When the `legacy` runner has been removed, we don't have this issue anymore, because resolvers are only supported implementation of test resolution. Unfortunately, we kept validation of supported runners during the test reference resolution with hardcoded `nrunner`. This is wrong because `nrunner` is a `SuiteRunner` plugin, and it can be replaced by any installed `SuiteRunner`. Reference: avocado-framework#5954 Signed-off-by: Jan Richter <[email protected]>
Hi @pevogam, no it is not deprecated, the suite_runner is selected at different place. This code can be removed, because we had it only for distinguishing between legacy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, in this case this change is entirely welcome. Our plugin sets exactly that config option and it works well with the exception of exactly the code that was dropped. LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This drops our previous workaround which was reported as needed in avocado-framework/avocado#5954 and consequently resolved with the merge of the pull request avocado-framework/avocado#5955
This is a removal of left over of legacy code. When avocado supported
legacy
andnrunner
runners we also distinguished between resolver resolution and test load. When thelegacy
runner has been removed, we don't have this issue anymore, because resolvers are only supported implementation of test resolution. Unfortunately, we kept validation of supported runners during the test reference resolution with hardcodednrunner
. This is wrong becausenrunner
is aSuiteRunner
plugin, and it can be replaced by any installedSuiteRunner
.Reference: #5954