You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
--
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.
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
Describe the bug
I use Matter TH v2.11+fall2024 UI, but response like this:
--
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
The text was updated successfully, but these errors were encountered: