-
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
Fix kotlin test CI and android TV cast example CI #25644
Fix kotlin test CI and android TV cast example CI #25644
Conversation
PR #25644: Size comparison from bc8c9ec to d868801 Decreases (1 build for cc32xx)
Full report (2 builds for cc32xx, mbed)
|
d868801
to
ed4754e
Compare
PR #25644: Size comparison from bc8c9ec to ed4754e Full report (1 build for cc32xx)
|
ed4754e
to
2d2bddc
Compare
PR #25644: Size comparison from bc8c9ec to 2d2bddc Decreases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
0018e08
to
09198ce
Compare
PR #25644: Size comparison from bc8c9ec to 09198ce Decreases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
I saw all of IM commands (read/write/invoke/subscribe) are implemented within pairing cluster, but tested under another cluster 'im', under which clusters those commands are implemented in chip-tool? we need to align with chip--tool. Finally, we should auto-generated the command handlers from its xml cluster definition file |
09198ce
to
045e961
Compare
PR #25644: Size comparison from bc8c9ec to 045e961 Decreases (1 build for cc32xx)
Full report (2 builds for cc32xx, mbed)
|
these should be tested in im category, however, we don't have enough bandwidth to figure out how to extract the certs info and setup case connection in these im tests, in addition, standalone case api in jni is not ready. Would file the ticket on it. We may use zap to generate a list of test commands later, file the ticket as well. thanks |
#25650 is a FR and not imminent, I updated the description of #25649, this is not about test, the problem is in IM cluster commands implementation, currently, all IM cluster commands are registered under cluster 'im', but implemented as 'pairing' cluster command. The behavior is undefined, if we register a command in one cluster, but implemented it under another cluster. Lets follow-up this after this PR lands |
-- previous #25636 does not update python wrapper for kotlin im test runtest function, need add missing piece so that CI can pass
-- previous #25505 does not update the subscriptionId in OnEstablishedCallback in example android tv cast side. need update it.