-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
twister: add integration_toolchains support #82515
twister: add integration_toolchains support #82515
Conversation
|
f5723a1
to
c721948
Compare
5f6e67c
to
55730a9
Compare
9e91b51
to
182a7c8
Compare
this is now addressed |
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 - so is this an alternative to filtering based on toolchain or is it intended to replace filtering based on toolchain? Does it produce fewer skipped / filtered test results?
this adds another vector for testing where desired. Right now a test configurations is based on test scenario -> platforms1 -> toolchain1 where toolchain1 is whatever is configured in the environment. with this, it is possible to have: test scenario -> platforms1 -> toolchain1 |
934987b
to
31f3ff8
Compare
31f3ff8
to
f731d98
Compare
|
@@ -355,6 +355,8 @@ def json_report(self, filename, version="NA", platform=None, filters=None): | |||
suite["used_rom"] = used_rom | |||
|
|||
suite['retries'] = instance.retries | |||
if instance.toolchain: |
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.
isn't instance.toolchain
always set to some value ?
if itoolchain: | ||
toolchain = itoolchain | ||
else: | ||
default_toolchain = "zephyr" if not self.env.toolchain else self.env.toolchain |
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 think this logic is worth to mention in doc/develop/test/twister.rst
with the same probe, I've noticed some confusing log output, e.g.
better to change to something like:
|
Added integration_toolchains to allow building/testing with multiple toolchains available in the environment. This changes the output structure and adds another level in the path under twister_out signifying the toolchain used. The toolchain used (variant) is also part of the json output now. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Use new keyword integration_toolchains to build test using additional toolchains. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Document the new option and how to use integration_toolchains. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
f731d98
to
d4f940a
Compare
Added integration_toolchains to allow building/testing with multiple
toolchains available in the environment.
This changes the output structure and adds another level in the path
under twister_out signifying the toolchain used. The toolchain used
(variant) is also part of the json output now.