-
Notifications
You must be signed in to change notification settings - Fork 216
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
Remove run_master_restart_test
tests
#509
Comments
I think that more elaborate explanation on why to remove this test is needed. If we would remove all tests just because they are failing then we do not really need any tests at all. Could you please explain why specifically this test should be removed instead of being fixed? |
From my point of view. It tests unsupported functionality. And it would cost a lot of afford to investigate it. I've spent some time debugging it but without any success. It fails randomly. I have some thoughts on catching it, but I am unsure whether it is worth it. |
Hi, thank for your reply. Is there somewhere a list of supported functionality? So we could enclose it in the commit message in proceeding PR? |
Here, we have information about replication. It's just a proof-of-concept functionality. That's why I interpret it as unsupported. |
This issues is resolved by #510. Closing. |
Container platform
Podman/Docker
Version
No response
OS version of the container image
RHEL 8, RHEL 9, CentOS Stream 9
Bugzilla, Jira
No response
Description
It looks like the tests `` is failing on several platforms. I would remove it.
See logs here: #507
Reproducer
No response
The text was updated successfully, but these errors were encountered: