-
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
Make DM provider and ember encode errors the same #35338
Make DM provider and ember encode errors the same #35338
Conversation
…nit testing. Implement a separate flag to control if we crash on errors for IM/DM checks or not.
Co-authored-by: Boris Zbarsky <[email protected]>
Review changes with SemanticDiff. Analyzed 10 of 41 files. Overall, the semantic diff is 10% smaller than the GitHub diff. File Information
|
PR #35338: Size comparison from ce3b4d9 to ba70abf Full report (10 builds for nrfconnect, nxp, qpg, stm32, tizen)
|
PR #35338: Size comparison from ce3b4d9 to cc4e9e0 Full report (12 builds for nrfconnect, nxp, qpg, stm32, tizen)
|
PR #35338: Size comparison from ce3b4d9 to 27cf823 Increases above 0.2%:
Full report (77 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #35338: Size comparison from ce3b4d9 to 54734d3 Increases above 0.2%:
Full report (77 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #35338: Size comparison from 44f8837 to 9805dde Full report (77 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #35338: Size comparison from 44f8837 to 8eb3645 Full report (77 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #35338: Size comparison from 44f8837 to 5c0af60 Full report (77 builds for bl602, bl702, bl702l, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
* The flag of CONFIG_BUILD_FOR_HOST_UNIT_TEST is not actually tied to unit testing. Implement a separate flag to control if we crash on errors for IM/DM checks or not. * Update src/app/common_flags.gni Co-authored-by: Boris Zbarsky <[email protected]> * make the flag name singular * Add unit test cluster members * Modified zap and made these attributes optional * Zap regen * Attributes MUST be up to 0x4FFF so needed to switch codes * Update ids enabling * Move around things and add unit test * Update to run unit tests with enforced DM checking * Comment describing the updated options * Fix unit test * Restyle * Kotlin format since it seems different eforcement is going on here * Update src/app/zap-templates/zcl/data-model/chip/test-cluster.xml Co-authored-by: Boris Zbarsky <[email protected]> * Update examples/all-clusters-app/linux/main-common.cpp Co-authored-by: Boris Zbarsky <[email protected]> * Remove redundant using * Simplify/shorten code * Move base to 0x3000 for the new attributes for test cluster testing * Restyle * Fix python unit test * Fix all clusters app * Fix unused import in python * Zap regen * Fix cirque * Fix hardcoded paths in TestTimeSyncTrustedtimeSourceRunner.py * Typo fix * Remove extra spacing * Update text * Fix app path --------- Co-authored-by: Andrei Litvin <[email protected]> Co-authored-by: Boris Zbarsky <[email protected]>
Changes