-
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
Timeouts in Darwin seem to be capped at a max of 3 secs , some of the TC require upto 15 secs in some cases #14260
Comments
@raju-apple Care to update the zapt file? If not, someone can take a look! |
So it looks like the chip-tool version of this has a timeout for an entire .yaml file (currently set at 90s), while the Darwin version has a per-step timeout (3s). We can certainly bump the Darwin timeout. What value would be useful there? We can also add a way to specify a longer-than-default timeout for a given test step directly in the yaml, possibly in combination with also bumping the default to cover more cases. @raju-apple Preferences? |
@bzbarsky-apple I like the second option , yeah if the yaml has a timeout specified in the step we should pick that up and if not it can fall back to the default. Maybe make the default as 5s or do you think its too much of a bump ? |
5s default is easy. Let me do this. :) |
This makes the following changes: 1) Bumps kTimeoutInSeconds from 3 to 5. 2) For "WaitForMs" commands, sets the timeout to (waitTime/1000) + kTimeoutInSeconds, so longish waits work automatically. 3) Allows specifying a "stepTimeoutSecs" property in the YAML to override all of that and just set a value. Fixes project-chip#14364 Fixes project-chip#14260
This makes the following changes: 1) Bumps kTimeoutInSeconds from 3 to 5. 2) For "WaitForMs" commands, sets the timeout to (waitTime/1000) + kTimeoutInSeconds, so longish waits work automatically. 3) Allows specifying a "stepTimeoutSecs" property in the YAML to override all of that and just set a value. Fixes #14364 Fixes #14260
…ect-chip#14368) This makes the following changes: 1) Bumps kTimeoutInSeconds from 3 to 5. 2) For "WaitForMs" commands, sets the timeout to (waitTime/1000) + kTimeoutInSeconds, so longish waits work automatically. 3) Allows specifying a "stepTimeoutSecs" property in the YAML to override all of that and just set a value. Fixes project-chip#14364 Fixes project-chip#14260
Is this by design ?
Probably the issue could be related to this :
https://github.com/project-chip/connectedhomeip/blob/master/src/darwin/Framework/CHIP/templates/clusters-tests.zapt#L22
Can this be fixed ? Blocking us from adding a few CC test cases.
The text was updated successfully, but these errors were encountered: