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

[Bug] Test Step Error: Error occurred during execution of test case TC-ACL-2.7. Connecting to ws://172.18.0.1:9002 failed. #520

Open
Cj-S1dTy opened this issue Jan 16, 2025 · 5 comments
Assignees
Labels

Comments

@Cj-S1dTy
Copy link

Describe the bug

I use Matter TH v2.11+fall2024 UI, but response like this:

  • Test Step Error: Error occurred during execution of test case TC-ACL-2.6. sent 1011 (internal error) keepalive ping timeout; no close frame received
    --
  • Test Case Completed [ERROR]: TC-ACL-2.6
  • ================================================================================
  • ================================================================================
  • Executing Test Case: TC-ACL-2.7 (Semi-automated)
  • YAML Version: f2e5de7e7978dd0748ba014f7b6ce593dad2fc88

  • Executing Test Step: Start chip-tool test
  • Using PICS file: /var/tmp/pics
  • Test Step Error: Error occurred during execution of test case TC-ACL-2.7. Connecting to ws://172.18.0.1:9002 failed.
  • Test Case Completed [ERROR]: TC-ACL-2.7 (Semi-automated)
  • ================================================================================
  • ================================================================================
  • Executing Test Case: TC-ACL-2.8 (Semi-automated)
  • YAML Version: f2e5de7e7978dd0748ba014f7b6ce593dad2fc88

  • Executing Test Step: Start chip-tool test
  • Using PICS file: /var/tmp/pics

Steps to reproduce the behavior

No response

Expected behavior

No response

Log files

No response

PICS file

pics.zip

Screenshots

Environment

Version: v2.11+fall2024
Sha: 8f86ccd

Additional Information

No response

@Cj-S1dTy Cj-S1dTy added Bug Something isn't working Needs Triage labels Jan 16, 2025
@antonio-amjr
Copy link
Contributor

antonio-amjr commented Jan 20, 2025

Hi @Cj-S1dTy

I could not reproduce the errors you mentioned above on the latest version of Test-Harness (TH).
Thanks for sharing the PICS files you used, but we lack more information.
Could you please provide more files like the test and DUT logs, the TH versions you used, the configuration from the TH's UI, etc.

@Cj-S1dTy
Copy link
Author

TH version:v2.11+fall2024 Sha: 8f86ccd

@Cj-S1dTy
Copy link
Author

@Cj-S1dTy
Copy link
Author

Hi @antonio-amjr ,Attached is the latest test log documenting the same problem in the ACL

UI_Test_Run-Access Control_2025_01_21_18_25_19.log

@antonio-amjr
Copy link
Contributor

antonio-amjr commented Jan 22, 2025

Hi @Cj-S1dTy

Taking a look in the logs and the example in the description, I believe the real issue here is the error keepalive ping timeout; no close frame received that happens executing TC-ACL-2.6 and triggers the "connecting to ws..." error for all following tests executed after.

For the record, this behavior was mentioned before in the comment #273 (comment) where a "Keepalive ping timeout" error also happened and triggering subsequent errors for others tests as well.

This problem is being tracked by issue#29194 of the SDK team (connectedhomeip repo) but I'm not aware of any news on that matter.


In my case I'm not able to reproduce this issue so I'm wondering if anything else is different in our environment.
So a couple of question for you would be:

  • What's the ubuntu version?
  • Is a real DUT being used? (please provide the logs from the DUT, maybe could help)
  • Is the v2.11+fall2024 updated? The SHA being used is not the latest

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

No branches or pull requests

2 participants