-
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
Wait at least max_report_interval_sec for subscription report update #36771
Wait at least max_report_interval_sec for subscription report update #36771
Conversation
Changed Files
|
0097547
to
b10b919
Compare
b10b919
to
07d25b3
Compare
PR #36771: Size comparison from 73cc4f1 to 07d25b3 Full report (69 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
This PR does not solve the timeout when running test with |
We have a logic bug in test script, max_report_interval_sec is set to 30s, but we only wait 10s, now I change the max_report_interval_sec to 10, and we wait up to 10 +1 seconds, in theory, we should receive the subscription report within this window, if not, it indicates there is some issues on subscription specific to fabric-sync |
We discovered that the TH might fail to receive the subscription report update before the timeout in in MCORE-FS-1.5 step 10