mirror of
https://github.com/codership/wsrep-lib.git
synced 2026-10-23 09:48:57 +03:00
fbadbdd2a7
branch The existing regression tests for the missing after_apply() cleanup did not exercise every failing call site: apply_fragment()'s fragment-removal block only had a test for its trailing commit() failing, leaving remove_fragments() itself untested, and commit_fragment()'s apply_err branch (a separate "ret || (after_apply(), 0)" site, reached when applying the last fragment itself fails) had no coverage at all. Add tests for both, plus a passing coverage check that rollback_fragment()'s own fragment-removal block -- which already calls after_apply() unconditionally -- doesn't regress into the same short-circuit idiom. Add a fail_next_remove_fragments_ hook to mock_high_priority_service to allow simulating a storage-engine level failure while removing streaming fragments.