Closed Rajashreekalmane closed 2 months ago
Only TC-CCTRL-2.2 and, TC-MCORE_FS_1_1 have issues with running back to back.
The issue is they leave the shell TH_SERVER application running because they set the shell=True
.
TC-MCORE_FS_1_2 doesn't have issues running back-to-back, but is has issues running after TC-CCTRL-2.2 and, TC-MCORE_FS_1_1 as the port number used by the test (5543) is occupied by the application that never properly terminated
I've noticed that after rebooting the RPI, the TCs pass successfully. However, if I run the TCs back-to-back, even the same TC that initially passed will fail.
Todays live debug sesssion between Rajashreekalmane and myself determined that the issue of running back to back is only for
We noticed some flake with
This flake is not something I can look into before SVE. But I can fix the back to back issues as it requires a similar fix as https://github.com/project-chip/connectedhomeip/pull/35257
Feature Area
Other
Test Case
TC-CCTRL-2.2, TC-MCORE_FS_1_1 and TC-MCORE_FS_1_2
Reproduction steps
Issue Summary: Back-to-back runs of the test cases TC-CCTRL-2.2, MCORE_FS_1_1, and MCORE_FS_1_2 fail because the TH does not properly terminate the TH_SERVER application. This issue affects both the Fabric Synchronization and Commissioner Control clusters, leading to timeout errors during secure session establishment in subsequent test executions.
Steps to Reproduce:
sudo rm -rf /tmp/chip_* && ./fabric-admin
./fabric-bridge-app
Execute the following command:
python3 TC_CCTRL_2_2.py --commissioning-method on-network --discriminator 3840 --passcode 20202021 --paa-trust-store-path ../../credentials/development/paa-root-certs/ --storage-path admin_storage.json --string-arg th_server_app_path:/home/ubuntu/Aug7/connectedhomeip/examples/all-clusters-app/linux/out/all-clusters-app/chip-all-clusters-app
Note: The reference app path used is /home/ubuntu/Aug7/connectedhomeip/examples/all-clusters-app/linux/out/all-clusters-app/chip-all-clusters-app. After successfully validating TC_CCTRL_2_2, attempt to validate TC_MCORE_FS_1_1:python3 TC_MCORE_FS_1_1.py --commissioning-method on-network --discriminator 3840 --passcode 20202021 --paa-trust-store-path ../../credentials/development/paa-root-certs/ --storage-path admin_storage.json --string-arg th_server_app_path:/home/ubuntu/Aug7/connectedhomeip/examples/all-clusters-app/linux/out/all-clusters-app/chip-all-clusters-app
Bug prevalence
Everytime
GitHub hash of the SDK that was being used
9c2d570f7852438c832622a8c1b6ba395ffb1711
Platform
raspi
Anything else?
Expected Behavior: The TH_SERVER application should terminate properly after the completion of each test case, allowing subsequent runs of TC-CCTRL-2.2, MCORE_FS_1_1, and MCORE_FS_1_2 without issues.
Actual Behavior: The TH_SERVER fails to terminate, causing the following error during subsequent test runs:
PFA log below : Fabric admin.txt Fabric-bridge-app.txt python script validation log.txt