Closed richtja closed 5 months ago
Hi @pevogam, when you will have time, can you please check if this fixes your issue in #5954, thank you.
Hi @pevogam, when you will have time, can you please check if this fixes your issue in #5954, thank you.
Hi @richtja, but I don't understand - is this run.suite_runner
config option now deprecated? Because the diff in the fix simply seems to remove it.
Hi @pevogam, when you will have time, can you please check if this fixes your issue in #5954, thank you.
Hi @richtja, but I don't understand - is this
run.suite_runner
config option now deprecated? Because the diff in the fix simply seems to remove it.
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 loader
and nrunner resolver
. Actually, this part of the code has nothing to do with the suite_runner
itself, and therefore it can be removed. For more information about this, you can look into last LTS version with the legacy runner.
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