project-chip / project-chip/certification-tool

[Bug] [TC_SU_2.2] Test Case Status Shows Pending After Successful Execution

Open
#891 6 comments 0 reactions 2 assignees View on GitHub

@rquidute is already working on this.

Since Mar 25, 2026.

Awaiting Originator Feedback Bug Needs Triage
Dominant language
Shell
Stars
82
Forks
47
Avg merge
1d 15h
Merged PRs (30d)
17

Description

Description:

While executing the TC_SU_2.2 test case using the TH, all the test steps were completed successfully and the test case showed a pass status during execution.

However, while downloading the execution logs from the TH, the TH UI became unresponsive. After refreshing the TH page, the TC_SU_2.2 test case status was shown as Pending, even though all the steps had already been executed and passed. After refreshing/rebooting the TH, the complete log is disappeared.

For Reference Attached The video.

Steps to reproduce the behavior
  1. Build Procedure for the OTA Requestor App -- software version 2 :
    • In connectedhomeip repo build the app software version 2
    • Build OTA Requestor App – Software Version 2 Update the following fields in

~/connectedhomeip/config/standalone$ nano CHIPProjectConfig.h

Set:
#define CHIP_DEVICE_CONFIG_DEVICE_SOFTWARE_VERSION 2
#define CHIP_DEVICE_CONFIG_DEVICE_SOFTWARE_VERSION_STRING "2.0"
Then build the OTA Requestor App for software version 2 :
  1. Then build the OTA Requestor App for software version 2 :
    • scripts/examples/gn_build_example.sh examples/ota-requestor-app/linux out/debug_v2 chip_config_network_layer_ble=false

3 . Stripped binary using the ota-requestor-app build :

  • -strip --strip-all "out/debug_v2/chip-ota-requestor-app" -o "out/debug_v2/chip-ota-requestor-app.min"

4 . Generated OTA Image using the build of software version 2 (.ota file) -

src/app/ota_image_tool.py create \
-v 0xFFF1 \
-p 0x8000 \
-vn 2 \
-vs "2.0" \
-da sha256 \
out/debug_v2/chip-ota-requestor-app.min \
out/debug/ota-requestor-app_v2.ota

5 .OTA Image Deployment to DUT (Raspberry Pi):

  • After generating the OTA image (ota-requestor-app_v2.ota) from the connectedhomeip repository, copy the image file to the Raspberry Pi DUT where the OTA Requestor application is running.

Login to the Raspberry Pi and navigate to the application directory:

ubuntu@raspberrypi:~$ cd ~/apps     

Copy the generated OTA image (ota-requestor-app_v2.ota) from the host machine to the DUT’s application directory :

ubuntu@raspberrypi:~/apps$ sudo cp ota-requestor-app_v2.ota /var/credentials/development/    

Test Parameters Used for Executing TC_SU_2_2 In TH :

  • The following test parameters were configured in the Test Harness to execute the TC_SU_2_2 test case:

"test_parameters": {
     "endpoint": "0",
     "timeout": "600",
     "string-arg": "provider_app_path:/root/apps/chip-ota-provider-app   ota_image:/credentials/development/ota-requestor-app_v2.ota",
     "int-arg": "ota_provider_port:5541"
   },
  • Start the DUT chip-ota-requestor-app (defaults to version 1) .

    • ./chip-ota-requestor-app --KVS /tmp/chip_kvs_requestor
  1. Execute the TC_SU_2_2 test case using the TH.
  2. Observe that all the test steps are completed and marked as pass.
  3. Attempt to download the execution logs from the TH.
  4. Refresh the TH page after the UI becomes unresponsive.
  5. Observe that the TC_SU_2_2 test case status is displayed as Pending.
Expected behavior

After successful execution and completion of all test steps, the TC_SU_2.2 test case status should be updated and retained as Pass, even after downloading logs or refreshing the TH page.

Screenshots

https://github.com/user-attachments/assets/3598727e-e8e5-4958-ba28-52194229f84f

Environment

Version: v2.15-beta2.2+spring2026
Sha: 28fa53b

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.