-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Documentation for YAML tests #31575
Documentation for YAML tests #31575
Conversation
Pulls from the test harness presentations in Korea and Geneva
PR #31575: Size comparison from 0ff709f to bca5a7b Full report (73 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, stm32, telink)
|
PR #31575: Size comparison from 0ff709f to 8f8d2f6 Full report (45 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, stm32)
|
PR #31575: Size comparison from 0ff709f to a0e49f3 Full report (73 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, stm32, telink)
|
PR #31575: Size comparison from 0ff709f to 7b5d182 Full report (73 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, stm32, telink)
|
PR #31575: Size comparison from 0ff709f to 8a03f47 Full report (7 builds for cc32xx, mbed, nrfconnect, stm32)
|
PR #31575: Size comparison from 0ff709f to b2922ed Full report (73 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, stm32, telink)
|
PR #31575: Size comparison from 0ff709f to ee2f902 Full report (9 builds for cc32xx, mbed, nrfconnect, qpg, stm32)
|
PR #31575: Size comparison from 0ff709f to c1960d7 Increases above 0.2%:
Increases (2 builds for efr32, linux)
Decreases (2 builds for efr32, linux)
Full report (73 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, stm32, telink)
|
@@ -0,0 +1,35 @@ | |||
<!--- |
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.
Something seems off with the end result, when looking at preview and what got merged in github
https://github.com/project-chip/connectedhomeip/blob/master/docs/testing/yaml_schema.md
"-->\n\n") | ||
|
||
|
||
def get_type_list_and_vars(typetuple) -> (list[type], bool): |
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.
nit, please add function documentation to explain what the tuple return is. It wasn't originally obvious what the what the bool was for
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.
added - the bool is whether variables are supported.
try: | ||
typelist = list(typetuple) | ||
if str in typelist: | ||
reduced = [t for t in typelist if t != str] |
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.
If I am being honest I don't actually understand the t != str
is checking here? I would expect either:
t != "str"
, or isinstance(t, str)
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.
yeah, it's a comparison to a class. It's not an instance though - it's the class of the type, which is why it looks weird. ie, the yaml parser has a tuple of classes that are allowed. So t will directly be str class, rather than an instance of the class or a string of the class name. That happens because the parser is coded weirdly. I've added a comment to explain.
Includes material from https://groups.csa-iot.org/wg/matter-csg/document/29088 and https://groups.csa-iot.org/wg/matter-csg/document/32281.