-
Notifications
You must be signed in to change notification settings - Fork 8.3k
twister: support namespacing of extra configs #53725
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
Conversation
91b2f2f to
f3a35c3
Compare
We want to be able to have platform or architecture extra configs without having to duplicate a whole section of the test specification. This adds support for namespacing of extra configs, for example: arch:nios2:CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000 or platform:qemu_x86:CONFIG_FOO=y Signed-off-by: Anas Nashif <anas.nashif@intel.com>
|
Works great! Could this be done for 'west build' too? |
But |
|
west has option --test-item where one can point to a particular scenario from yestcase/sample.yaml and west would build with using extra_args from yaml. I guess it can (or in fact should, for complementary?) updated as well. |
yeah, I actually tried using west like this before I realized the patch was only to twister... |
|
Could this namespacing feature be added to |
We want to be able to have platform or architecture extra configs
without having to duplicate a whole section of the test specification.
This adds support for namespacing of extra configs, for example:
arch:nios2:CONFIG_SYS_CLOCK_TICKS_PER_SEC=1000
or
platform:qemu_x86:CONFIG_FOO=y
Signed-off-by: Anas Nashif anas.nashif@intel.com