-
Notifications
You must be signed in to change notification settings - Fork 18
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
RouterTestSslInterRouter::test_connected_tls_sasl_routers, part of system_tests_ssl, takes a long time (>300s) #420
Comments
…ter QDR.A to connect to the other routers. This is not a fix for the issue
I added some prints in the associated PR. This is what I see locally -
Will be interesting to see what the CI reports. |
…ter QDR.A to connect to the other routers. This is not a fix for the issue
Such suspense, I could not resist and had a peek
Both 60 and 300 are values of |
…onnect to the other routers. This is not a fix for the issue (#423)
Not resolved, test still takes long time |
I did not use 'Fixes #420' in my commit message but that did not matter, the issue was still closed !!(??)!! |
I think that @kgiusti is responsible for that :P |
In any case, I get email when my issues get closed, and the issue list is still of manageable size, so I can remember context and scream "not fixed!" |
Gotcha ! Thanks. |
Closing this, might reopen if this problem shows up again. |
https://github.com/skupperproject/skupper-router/runs/6253209682?check_suite_focus=true#step:26:3238
Note the time difference between previous passing test at 06:48:43 and test_connected_tls_sasl_routers passing at 06:53:52.
[...]
It seems an invariable rule that the ssl tests always finish last.
After setting a 300s timeout per test (here meaning python test method), which is IMO still overly generous, the test gets reported as exceeding that timeout
https://github.com/skupperproject/skupper-router/runs/6263670044?check_suite_focus=true#step:26:3841
The text was updated successfully, but these errors were encountered: