-
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
TC-IDM-10.5: Device type conformance - Add #34424
Conversation
Initial test only looks at clusters. Remaining - revisions - feature conformance - cluster elements
PR #34424: Size comparison from e7380a1 to be752d6 Full report (75 builds for cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Then I can use it in the example.
PR #34424: Size comparison from e7380a1 to 0e6d6eb Full report (20 builds for cc13x4_26x4, cc32xx, mbed, nrfconnect, nxp, qpg, stm32, tizen)
|
PR #34424: Size comparison from e7380a1 to 4c1f585 Full report (85 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Let's go the other way and remove the cluster and the device type.
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.
The lock-app changes look good to me; someone who is closer to the Python testing stuff than I am should review those changes.
PR #34424: Size comparison from c0d76b3 to 6625f3d Full report (57 builds for bl602, bl702, bl702l, cc32xx, esp32, linux, mbed, nxp, qpg, stm32, telink, tizen)
|
PR #34424: Size comparison from c0d76b3 to 6170f0a Increases above 0.2%:
Full report (82 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, mbed, nxp, psoc6, qpg, stm32, telink, tizen)
|
* TC-IDM-10.5: Device type conformance - Add Initial test only looks at clusters. Remaining - revisions - feature conformance - cluster elements * Restyled by autopep8 * Restyled by isort * Add OTA requestor device type to door lock Then I can use it in the example. * add test to CI * linter * OTA requestor isn't hooked up, remove Let's go the other way and remove the cluster and the device type. * Revert "OTA requestor isn't hooked up, remove" This reverts commit b4bde38. * Revert "Add OTA requestor device type to door lock" This reverts commit 51edb79. * Remove from CI until door lock OTA is sorted. --------- Co-authored-by: Restyled.io <commits@restyled.io>
* TC-IDM-10.5: Device type conformance - Add Initial test only looks at clusters. Remaining - revisions - feature conformance - cluster elements * Restyled by autopep8 * Restyled by isort * Add OTA requestor device type to door lock Then I can use it in the example. * add test to CI * linter * OTA requestor isn't hooked up, remove Let's go the other way and remove the cluster and the device type. * Revert "OTA requestor isn't hooked up, remove" This reverts commit b4bde38. * Revert "Add OTA requestor device type to door lock" This reverts commit 51edb79. * Remove from CI until door lock OTA is sorted. --------- Co-authored-by: Restyled.io <commits@restyled.io>
Initial test only looks at clusters. Remaining