Skip to content
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

Python controller unpair failed with ChipStackError: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout #37652

Open
Saravana-kr22 opened this issue Feb 19, 2025 · 1 comment
Assignees

Comments

@Saravana-kr22
Copy link
Contributor

Saravana-kr22 commented Feb 19, 2025

Description
When executing the script TC_Android_pair.py as a part of stress testing, unpairing function is failed with the chip.exceptions.ChipStackError: src/lib/address_resolve/AddressResolve_DefaultImpl.cpp:124: CHIP Error 0x00000032: Timeout error. This script will mimic on a high level how the pairing occurs in the Android ecosystem.

GitHub hash of the SDK that were being used are : 92f9f0b

Platforms
I Have performed the execution on Raspberrypi using ble-thread provisioning
Test Bed :
Controller Platform - python controller running on Raspberrypi 4B -8GB,
Nordic Board as DUT - all-cluster-app running on Nordic nrf52840-DK board
Provisioning method - ble-thread

Test scenario
Pair/Provision the DUT (All-cluster-app running on raspi) as per Android pairing flow using Ble-Thread.
Read device information after the device is provisioned
Unpair the DUT (i.e. removing the fabric)
Factory reset the DUT
repeat step1 - 6 for 500 iterations
Script reference: https://github.com/CHIP-Specifications/matter-qa/blob/main/src/matter_qa/scripts/reliability_scripts/TC_Android_Pair.py

Execution Details

In this Test bed for Iteration [ 91, 92, 96, 138, 59] are failed to unpair.
Iterations scheduled to run: 200
Iterations Failed: 5
Iterations Passed: 195
Execution Logs (logs consists of 4 Pass iteration:[58,60,95,97] and 5 Fail Iterations):

passed_58.zip
failed_59.zip
passed_60.zip
failed_91.zip
failed_92.zip
failed_138.zip
passed_95.zip
failed_96.zip
passed_97.zip

@cjandhyala
Copy link
Contributor

@Damian-Nordic Could you pls take a look at this issue ?

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

No branches or pull requests

3 participants