Closed clebergnu closed 3 months ago
Hi @richtja, thanks for the review. I've addressed both issues, and explained the additional changes to the verification of values in the commit message, reading:
Because the purpose of the default_config and config are different,
the checks for the values they may contain are different. The
default_config should contain the exact keys as in the used config.
The config itself, on the other hand, may contain nothing, or some
values, but it should never be more than a subset of the config.
Hi @clebergnu, thanks for the update. I just noticed that
Runnable.from_avocado_config
is also used insysinfo
plugin, can you please update that as well, so we won't use deprecated code in avocado plugins. Thanks
Good catch! Just updated it! Thanks!
Merging based on @richtja approval and CI status.
This change allows for the a runnable configuration and the suite and default configuration to coexist with the correct behavior.
In short, if the suite has a configuration, it will become the new default configuration for a runnable, while its own configuration will not be touched.
Fixes: https://github.com/avocado-framework/avocado/issues/5998