-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Randomize IP addresses during checkpoint/restore tests #3501
Conversation
Can one of the admins verify this patch?
|
Looks pretty good on the first try, no checkpoint/restore related failures. Let's try a second time. |
Second CI run also without errors. |
☔ The latest upstream changes (presumably #3496) made this pull request unmergeable. Please resolve the merge conflicts. |
This tries to reduce CI errors which might happen due to parallel CI runs which all are using the same IP addresses. Using random addresses should reduce the possibility of parallel tests using the same IP address. Signed-off-by: Adrian Reber <areber@redhat.com>
Rebased, repushed and removed WIP from title. Not sure if this actually makes sense or if it is a useless optimization. The first two CI runs looked pretty good, not sure if I am just lucky. |
LGTM |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianreber, mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There have been CI failures with some checkpoint/restore tests which could be related to running tests in parallel and using the same IP address.
This tries to run all (almost) checkpoint/restore tests with random IP addresses.