-
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
Increase CASE timeout to fix CI failures #11435
Conversation
Fast tracking to unblock test failures. @pan-apple can you file a follow up to look at retries? |
PR #11435: Size comparison from 3295ca0 to b5298e0 Decreases (1 build for esp32)
Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Yes we need a follow-up, because there should be NO retries on localhost against itself, which is what CI does, and if there is an ENOBUF that causes it to be a retry, we should not run out of 3 retries, unless something deeper is wrong. I want to make sure we are not masking a bug here. |
Filed this issue: #11440 |
/rebase |
b5298e0
to
e8fedc6
Compare
PR #11435: Size comparison from 29747a2 to e8fedc6 Full report (38 builds for efr32, esp32, k32w, linux, mbed, nrfconnect, p6, qpg, telink)
|
Problem
Darwin CI is failing sporadically in CASE establishment. The sender timeouts after sending the message (Sigma1) while it's waiting for response (Sigma2).
Change overview
The CASE message timeout is 10 seconds, which may be a bit low for CI and virtualization. Increasing it to 30 seconds for time being.
Testing
TestCASESession runs the existing unit tests related to this change.