-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
test(systest): avoid host volume mount in minio test #8569
Conversation
be9222e
to
bdc89f9
Compare
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.
Looks good to me. Please take a look at some comments above.
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.
@aman-bansal - this looks good to merge. Thanks!
The above comments are nitpicks .. and can be addressed when we move to compose tool later.
I have re-triggered a CI run .. once you have all passing - pls merge this off. |
Test failure seems relevant to the change. @mangalaman93 highlighting it for you.
|
I think this should be hitting
|
related PR #8576 (comment) |
The host mount would have files created as root causing the cleanup to fail on the CI.
bdc89f9
to
26d1f15
Compare
I have no idea how these tests have been passing. It could be because of differences in the docker version or something. I have fixed the tests now. |
there was a bunch of docker related issues which we have also fixed in the It could be something related to host-networking as well... sorry to have rabbit-holed you into this. |
yeah, it is a bit cleaner now and I will spend some time after slash main alignment on improving our test infra. |
instead of a host mount, we do everything inside the container now. This avoids creating any files on the host and the delete error on during cleanup on the CI do not happen.