-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Darwin] Track last commissioining stage for metrics #40010
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
base: master
Are you sure you want to change the base?
[Darwin] Track last commissioining stage for metrics #40010
Conversation
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.
Code Review
This pull request improves commissioning metrics on Darwin by preventing the kCleanup
stage from overwriting the actual final commissioning stage. The change correctly ignores the cleanup stage, which is particularly useful for diagnosing failures. The review suggests using a safer string comparison and simplifying the conditional logic to improve robustness and readability.
PR #40010: Size comparison from d8d0bc6 to abe4493 Full report (6 builds for cc32xx, nrfconnect, stm32)
|
- Since kCleanup is always called during commissioining it ends up being the last stage tracked. This fix is to ignore this stage and track the last stage committed as part of commissioining. Fixes project-chip#40009
abe4493
to
f3b0767
Compare
PR #40010: Size comparison from 3eac2cc to a0898e8 Full report (59 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
PR #40010: Size comparison from 3eac2cc to 2efc217 Full report (59 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
CI didn't pass on first try due to #40132 |
Summary
Related issues
Testing
Readability checklist
The checklist below will help the reviewer finish PR review in time and keep the
code readable:
descriptive
“When in Rome…”
rule (coding style)
See: Pull Request Guidelines