-
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
[Build] Test failed: src/messaging/tests/TestExchangeMgr.cpp:189: assertion failed: "!sendDelegate.IsOnResponseTimeoutCalled" '#3:','Test session eviction in timeout handling #27479
Comments
this has nothing to do with YAML or python. |
I am guessing we lost timeslice for > 100ms, so the timeout actually fired.... |
Thanks, renaming! |
In particular:
Note the 139ms time gap between previous test completion and us logging our send.... That's us losing the timeslice. There's really no way to win here. We could bump the exchange timeout value to make this less likely, but of course then the test will always run slower.... and nothing guarantees that we won't lose the timeslice for a longer time either. |
@bzbarsky-apple Let's up the timeout significantly here, it won't slow the test down that much compared to overall runtime. |
We could get into a situation where we lost the timeslice after the SendMessage call and before we asserted the response timeout had not happened yet, which would cause the test to fail. The changes here are: 1) Move the assert that we are not timed out to _before_ SendMessage(). This ensures that our state is correct up front, and generally nothing under SendMessage proper or sending the message should trigger a timeout per se. 2) Use more slack when waiting for the timeout, just in case. Fixes project-chip#27479
We could get into a situation where we lost the timeslice after the SendMessage call and before we asserted the response timeout had not happened yet, which would cause the test to fail. The changes here are: 1) Move the assert that we are not timed out to _before_ SendMessage(). This ensures that our state is correct up front, and generally nothing under SendMessage proper or sending the message should trigger a timeout per se. 2) Use more slack when waiting for the timeout, just in case. Fixes project-chip#27479
We could get into a situation where we lost the timeslice after the SendMessage call and before we asserted the response timeout had not happened yet, which would cause the test to fail. The changes here are: 1) Move the assert that we are not timed out to _before_ SendMessage(). This ensures that our state is correct up front, and generally nothing under SendMessage proper or sending the message should trigger a timeout per se. 2) Use more slack when waiting for the timeout, just in case. Fixes #27479
Build issue(s)
https://github.com/project-chip/connectedhomeip/actions/runs/5376188056/jobs/9753037388?pr=27470
Platform
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: