-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add code to MR for tcp_max_syn_backlog test #499
Conversation
looks like it reached the timeout limit (15m), we need to increase it.
|
Changed to 20 mins and works fine now. |
It's Friday and almost end of the day for some countries in Europe, @dennisbrendel or @priyverm might have some ideas if he is around. Otherwise, I will try to look dig it later today. I think Yariv is already kind of busy travelling outside his country for the conference to review this one. |
Signed-off-by: Nikolai Sednev <nsednev@redhat.com>
Yes, its a holiday in here Today, I'm just trying to cover what I can till the next week. |
Title: Validate if tcp_max_syn_backlog network parameter on Host can be resilient against random changes of this parameter in QM.
Description: The purpose of this test script is to validate if tcp_max_syn_backlog parameter value on Host, can be resilient against random changes of this parameter in QM. This is validated by creating a test environment, that generates and sets a random tcp_max_syn_backlog value in range from 128 to 1024 in QM and as soon as QM gets a new value, the test verifies that tcp_max_syn_backlog parameter on Host stays the same and not changes because of the QM network changes.
Expected result: PASS: tcp_max_syn_backlog parameter's value on Host stays the same.
Jira: VROOM-19564