Okay, after discussing with Valeriy, the approach to get this right is to:
1) Yank out the tests that attempt to reset state in order to test a particular scenario (reset replica_state to out_of_sync and attempt promoting as user, and as admin; reset replica_state to error and attempt to promote; reset replica_state to out_of_sync and attempt re-syncing); or:
2) Allow for such tests to have more meaning by introducing an API to enable/disable periodic replica update on demand, per share.
We can discuss these solutions, but can I put up a patch to sanely turn off these tests for the dummy driver?
Okay, after discussing with Valeriy, the approach to get this right is to:
1) Yank out the tests that attempt to reset state in order to test a particular scenario (reset replica_state to out_of_sync and attempt promoting as user, and as admin; reset replica_state to error and attempt to promote; reset replica_state to out_of_sync and attempt re-syncing); or:
2) Allow for such tests to have more meaning by introducing an API to enable/disable periodic replica update on demand, per share.
We can discuss these solutions, but can I put up a patch to sanely turn off these tests for the dummy driver?