Automate Remaining Failure/Cancellation Tests
Open
warm-up
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
We've already automated a lot of failure tests. See the related regression test schedule [here](https://github.com/citusdata/citus/blob/master/src/test/regress/failure_schedule)
I'm listing the ones that are remaining.
- [ ] Deadlock detection
- [ ] 2PC recovery
- [x] Tenant isolation
- [x] master_move_shard_placement -> w/wout logical replication
- [x] MX metadata sync
No longer applicable items:
- Task-tracker -- this may require some investigation on understanding how it works first :)
- Call home
Contributor guide
Assessment
This issue has not been assessed yet.