-
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
[Fabrix-Sync] Fix ICD device commissioning process #36821
base: master
Are you sure you want to change the base?
Conversation
PR #36821: Size comparison from 6706f33 to 5a719ea Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
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.
@arkq at a recent SWTT standup we decided to try once again for stricter "require tests".
Could you please update the "testing" section to describe how this was tested in detail including a strong justification of why this is impossible to test in an automated fashion. We are making the "tested manually" bar intentionally annoying to avoid having all PRs marked as "tested manually" because it is easier.
This is something that currently exists in CI, so I wonder why the tests do not cover this. I would have expected some test changes to be possible.
@andy31415 The goal of all these fixes is to run fabric-sync python tests on CI. The same tests which check
I'm trying to adhere to that rule whenever possible :) |
Problem
It's not possible to pair ICD device with
app pair-device <node> <setupQRCode> --enable-icd-registration
because theResetForNextCommand
is called in the middle of the commissioning which disrupts internal state.Changes
PairingManager::OnCommissioningComplete
, so it can be passed toStartDeviceSynchronization
Testing
Tested locally that it's possible to pair ICD device.