-
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
[CI:DOCS] hack/perf/bz-2162111.sh: use custom network #17335
[CI:DOCS] hack/perf/bz-2162111.sh: use custom network #17335
Conversation
hack/perf/bz-2162111.sh
Outdated
$ENGINE_A network rm -f $network_name >> /dev/null || true | ||
$ENGINE_B network rm -f $network_name >> /dev/null || true | ||
$ENGINE_A network create $network_name >> /dev/null | ||
$ENGINE_B network create $network_name >> /dev/null |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason to not use random names? That would prevent all name conflicts.
Also I am missing where you remove the network after the test is done?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason to not use random names? That would prevent all name conflicts.
Easier debugging to know where it came from.
Also I am missing where you remove the network after the test is done?
I didn't intend to since it'll get remove on the next invocation. The other scripts may also leave containers etc. in storage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm with @Luap99 on this one. It is polite to clean up after oneself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like leaking test resources for no reason.
I expected all test to cleanup what they created, I understand keeping images because pulling is expensive but the rest not so much.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please note the ./hack
, it's not in ./test
. I am not arguing against any of these points but ask to apply different standards to these hacked scripts.
I'll repush with cleaning up nonetheless 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated. Added a commit on top to also clean up after the other benchmarks.
Create the containers with a custom network. It has an impact on the speed of container creation. Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
To leave not leave some artifacts arounds. Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
e3e2125
to
8aa3776
Compare
LGTM |
@giuseppe PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe, vrothberg 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 |
Create the containers with a custom network. It has an impact on the speed of container creation.
Signed-off-by: Valentin Rothberg vrothberg@redhat.com
@baude @edsantiago PTAL
Does this PR introduce a user-facing change?