-
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
fix "podman system prune networks" flake #15994
Conversation
Since by default the network config dir is shared in the e2e tests any other parallel running test could remove a network and cause this test to fail. Fixes containers#15990 Signed-off-by: Paul Holzinger <[email protected]>
@edsantiago 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.
Nice catch. Thank you for the quick work.
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago, Luap99, rhatdan 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 |
Restarted one flake, changes LGTM |
I got to thinking: it takes two to tango, no? If this test is failing because some other test is stepping on it, shouldn't we see failures in that other test too? And shouldn't that other test be fixed? Unfortunately I can't find any clear indications in my flake logs, and I tried reading the test code, and that didn't go so well. Anyhow, just wondering if there's another place in the tests where we need to do the tmpdir thing. |
The problem is that in that test file many test do podman system prune which also removes networks, the other test doesn't care if it removes more than it should. Generally speaking it may be more future proof if all system prune/reset tests would use their own network config dir to prevent causing failures in other network tests. |
/hold cancel thanks again |
Since by default the network config dir is shared in the e2e tests any
other parallel running test could remove a network and cause this test to
fail.
Fixes #15990
Does this PR introduce a user-facing change?