Remove test_restart_sync_no_center #5994
Conversation
This test is ANCIENT. "Center" was the original term for "Scheduler" back when only I was writing on this thing. Anyway, this test was behaving oddly. I'm shifting it to a gen_cluster test and I suspect that that will either help things to work, or at least will give us a lot more visibility about why it isn't working.
Unit Test Results 12 files ±0 12 suites ±0 6h 32m 58s ⏱️ + 13m 56s For more details on these failures and errors, see this check. Results for commit 2f1088d. ± Comparison against base commit 5c7d555. ♻️ This comment has been updated with latest results. |
There was a problem hiding this comment.
I think this test is redundant. We have test_restart and test_restart_sync that are covering this case already, aren't they?
I don't really understand the no_center reference. Even if "translated" to no_scheduler, it appears that the original intent of this test has been lost a while ago. I'm pretty sure there is a scheduler in this test
|
I'm ok removing it entirely. I've just pushed that change. |
fjetter
changed the title
This test is ANCIENT. "Center" was the original term for "Scheduler"
back when only I was writing on this thing.
Anyway, this test was behaving oddly. I'm shifting it to a gen_cluster
test and I suspect that that will either help things to work, or at
least will give us a lot more visibility about why it isn't working.