Skip to content
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

To remove decommission test from upstream #2075

Merged

Conversation

cniackz
Copy link
Contributor

@cniackz cniackz commented Apr 17, 2024

Objective:

To remove decommission test from upstream.

@ramondeklein
Copy link
Contributor

I know that this test is failing sometimes (sometimes it succeeds the next time). I guess we should determine why this test is failing before removing it. I guess it's there for a reason?

Copy link
Contributor

@ramondeklein ramondeklein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@allanrogerr
Copy link
Contributor

I believe that the test is generally unstable because it depends on several factors. Quickly checking how it it implemented; I believe that it can be tuned but this requires some effort.
However to @cniackz 's point - decommission is not an everyday event; saving it for release or "enterprise hardening" may be more sane for the time being at least.

@allanrogerr
Copy link
Contributor

LGTM

@cniackz
Copy link
Contributor Author

cniackz commented Apr 18, 2024

Thank you guys, hence removing it from upstream

@cniackz cniackz merged commit 509b170 into minio:master Apr 18, 2024
25 checks passed
@cniackz cniackz deleted the remove-decommission-test-from-upstream branch April 18, 2024 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants