connectedhomeip icon indicating copy to clipboard operation
connectedhomeip copied to clipboard

[1.3] Stress Test of Pair and Unpair on Raspi accessory Failed in some iterations

Open cjandhyala opened this issue 9 months ago • 0 comments

Reproduction steps

  1. Using ToT , build all-cluster-app on raspi and build the python controller.
  2. Using the stress test scripts, execute pair and unpair in a loop of iterations. Script flow is ,
  • Factory reset DUT (all-cluster-app running on raspi)
  • pair DUT (using on-network)
  • sleep 2 secs
  • unpair DUT
  • repeat the above steps in a loop.

Bug prevalence

random

GitHub hash of the SDK that was being used

8a4dffc5dd20d5343c6ea384390aeedb0c6b2e4c

Platform

raspi

Platform Version(s)

No response

Type

Core SDK Crash

Anything else?

multiple iterations failed with following Matter stack signature. logs attached for all these fail scenarios.

CommissionFailure(Pairing with DUT failed Reason src/app/CommandSender.cpp:328: CHIP Error 0x00000032: Timeout CommissionFailure(Pairing with DUT failed Reason src/protocols/secure_channel/CASESession.cpp:1984: CHIP Error 0x000000C9: No shared trusted root )) CommissionFailure(CommissionFailure(Pairing with DUT failed Reason src/app/ClusterStateCache.cpp:303: CHIP Error 0x00000010: Key not found ) CommissionFailure(Pairing with DUT failed Reason src/controller/python/ChipDeviceController-ScriptDevicePairingDelegate.cpp:89: CHIP Error 0x00000003: Incorrect state ))

logs.zip

cjandhyala avatar Apr 30 '24 21:04 cjandhyala