-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[TE8][TC-IDM-2.2] step 5 fails because wildcard reads can easily take longer than 10 seconds #16118
Comments
Also note that the verification steps for this step is wrong. It should be |
Please file an issue in https://github.com/CHIP-Specifications/chip-test-plans on the test plan verification step being wrong? |
bzbarsky-apple
added a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Mar 11, 2022
Adds a --timeout optional command-line argument (to match the one that test commands have). Also changes the default timeout for read/subscribe from 10s to 30s, because wildcard read/subscribe can take a while. project-chip#16118
woody-apple
pushed a commit
to bzbarsky-apple/connectedhomeip
that referenced
this issue
Mar 11, 2022
Adds a --timeout optional command-line argument (to match the one that test commands have). Also changes the default timeout for read/subscribe from 10s to 30s, because wildcard read/subscribe can take a while. project-chip#16118
bzbarsky-apple
added a commit
that referenced
this issue
Mar 15, 2022
Adds a --timeout optional command-line argument (to match the one that test commands have). Also changes the default timeout for read/subscribe from 10s to 30s, because wildcard read/subscribe can take a while. #16118
andrei-menzopol
pushed a commit
to andrei-menzopol/connectedhomeip
that referenced
this issue
Apr 14, 2022
…#16122) Adds a --timeout optional command-line argument (to match the one that test commands have). Also changes the default timeout for read/subscribe from 10s to 30s, because wildcard read/subscribe can take a while. project-chip#16118
Sounds like this was completed when the support was added to chip-tool to specify a timeout. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using wildcard reads with chip-tool then the internal 10 second timeout for such a read command is sometimes not enough because such reads can return many, many objects depending on the device.
The timeout behaviour should be handled differently and - in case of tools like chip-tool - should be changeable by a command line option.
The text was updated successfully, but these errors were encountered: