Skip to content

Conversation

Alami-Amine
Copy link
Contributor

@Alami-Amine Alami-Amine commented Oct 20, 2025

Summary

  • Calling discover commissionables command only diplays one discovery result and then exits
  • Documentation of chip-tool mentions that it should mention all discovered commissionables.

Testing

CI Testing

@github-actions
Copy link

github-actions bot commented Oct 20, 2025

PR #41545: Size comparison from c1f377d to d6003fe

Full report (37 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, nxp, psoc6, qpg, realtek, stm32, telink)
platform target config section c1f377d d6003fe change % change
bl602 lighting-app bl602+mfd+littlefs+rpc FLASH 1106918 1106918 0 0.0
RAM 178882 178882 0 0.0
bl702 lighting-app bl702+eth FLASH 661238 661238 0 0.0
RAM 134969 134969 0 0.0
bl702+wifi FLASH 837350 837350 0 0.0
RAM 124421 124421 0 0.0
bl706+mfd+rpc+littlefs FLASH 1070318 1070318 0 0.0
RAM 117261 117261 0 0.0
bl702l contact-sensor-app bl702l+mfd+littlefs FLASH 899416 899416 0 0.0
RAM 105540 105540 0 0.0
lighting-app bl702l+mfd+littlefs FLASH 983336 983336 0 0.0
RAM 109748 109748 0 0.0
cc13x4_26x4 lighting-app LP_EM_CC1354P10_6 FLASH 770804 770804 0 0.0
RAM 103312 103312 0 0.0
lock-ftd LP_EM_CC1354P10_6 FLASH 782560 782560 0 0.0
RAM 108472 108472 0 0.0
pump-app LP_EM_CC1354P10_6 FLASH 728372 728372 0 0.0
RAM 97380 97380 0 0.0
pump-controller-app LP_EM_CC1354P10_6 FLASH 712840 712840 0 0.0
RAM 97580 97580 0 0.0
cc32xx air-purifier CC3235SF_LAUNCHXL FLASH 554514 554514 0 0.0
RAM 205752 205752 0 0.0
lock CC3235SF_LAUNCHXL FLASH 587754 587754 0 0.0
RAM 205840 205840 0 0.0
efr32 lock-app BRD4187C FLASH 963328 963328 0 0.0
RAM 126332 126332 0 0.0
BRD4338a FLASH 757032 757024 -8 -0.0
RAM 256960 256960 0 0.0
window-app BRD4187C FLASH 1058772 1058772 0 0.0
RAM 122560 122560 0 0.0
esp32 all-clusters-app c3devkit DRAM 103440 103440 0 0.0
FLASH 1796188 1796188 0 0.0
IRAM 83862 83862 0 0.0
nrfconnect all-clusters-app nrf52840dk_nrf52840 FLASH 933232 933232 0 0.0
RAM 161317 161317 0 0.0
nxp contact mcxw71+release FLASH 692208 692208 0 0.0
RAM 61496 61496 0 0.0
lighting mcxw71+release FLASH 723720 723720 0 0.0
RAM 68156 68156 0 0.0
lock mcxw71+release FLASH 773976 773976 0 0.0
RAM 61940 61940 0 0.0
psoc6 all-clusters cy8ckit_062s2_43012 FLASH 1676940 1676940 0 0.0
RAM 213908 213908 0 0.0
all-clusters-minimal cy8ckit_062s2_43012 FLASH 1593556 1593556 0 0.0
RAM 211116 211116 0 0.0
light cy8ckit_062s2_43012 FLASH 1460100 1460100 0 0.0
RAM 197728 197728 0 0.0
lock cy8ckit_062s2_43012 FLASH 1492652 1492652 0 0.0
RAM 225448 225448 0 0.0
qpg lighting-app qpg6200+debug FLASH 837272 837272 0 0.0
RAM 127716 127716 0 0.0
lock-app qpg6200+debug FLASH 774052 774052 0 0.0
RAM 118692 118692 0 0.0
realtek light-switch-app rtl8777g FLASH 706760 706760 0 0.0
RAM 106912 106912 0 0.0
lighting-app rtl8777g FLASH 757856 757856 0 0.0
RAM 127236 127236 0 0.0
stm32 light STM32WB5MM-DK FLASH 470252 470252 0 0.0
RAM 141320 141320 0 0.0
telink bridge-app tl7218x FLASH 710662 710662 0 0.0
RAM 90552 90552 0 0.0
light-app-ota-compress-lzma-shell-factory-data tl3218x FLASH 797040 797040 0 0.0
RAM 41008 41008 0 0.0
light-app-ota-shell-factory-data tl7218x FLASH 788240 788240 0 0.0
RAM 93652 93652 0 0.0
light-switch-app-ota-compress-lzma-factory-data tl7218x_retention FLASH 715126 715126 0 0.0
RAM 51852 51852 0 0.0
light-switch-app-ota-compress-lzma-shell-factory-data tlsr9528a FLASH 748430 748430 0 0.0
RAM 70900 70900 0 0.0
light-switch-app-ota-factory-data tl3218x_retention FLASH 725278 725278 0 0.0
RAM 34600 34600 0 0.0
lighting-app-ota-factory-data tlsr9118bdk40d FLASH 602556 602556 0 0.0
RAM 108700 108700 0 0.0
lighting-app-ota-rpc-factory-data-4mb tlsr9518adk80d FLASH 820860 820864 4 0.0
RAM 92048 92048 0 0.0

@codecov
Copy link

codecov bot commented Oct 20, 2025

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 51.04%. Comparing base (2e08efe) to head (d6003fe).
⚠️ Report is 6 commits behind head on master.

Files with missing lines Patch % Lines
...mmands/discover/DiscoverCommissionablesCommand.cpp 0.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master   #41545   +/-   ##
=======================================
  Coverage   51.04%   51.04%           
=======================================
  Files        1384     1386    +2     
  Lines      100937   100956   +19     
  Branches    13059    13061    +2     
=======================================
+ Hits        51521    51534   +13     
- Misses      49416    49422    +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Alami-Amine Alami-Amine changed the title [Just Testing] make discover commissionables return a list of all discovered devices instead of only one Oct 21, 2025
@Alami-Amine Alami-Amine changed the title make discover commissionables return a list of all discovered devices instead of only one [chip-tool] make discover commissionables return a list of all discovered devices instead of only one Oct 21, 2025
LogErrorOnFailure(RemoteDataModelLogger::LogDiscoveredNodeData(nodeData));

if (mDiscoverOnce.ValueOr(true))
if (mDiscoverOnce.ValueOr(false))
Copy link
Contributor

@bzbarsky-apple bzbarsky-apple Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is documented as defaulting to true, no?

As in, the documented behavior matches the implemented behavior. I am not sure where "Documentation of chip-tool mentions that it should mention all discovered commissionables" comes from. If it's from some sort of out-of-band documentation, that just means that documentation is wrong...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you need it to be defaulted as True? as it seems incoherent with the even the name of the command commissionableS

Copy link
Contributor

@bzbarsky-apple bzbarsky-apple Oct 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's possible the guide was written before this option was introduced; the dangers of out-of-band documentation. Like #25223 (thank you for finding that) explains, the option defaults to true to match the Python harness behavior, so that YAML and Python tests behave the same wrt discovery.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants