Closed onurctirtir closed 1 year ago
We should at least have one such target for one of the columnar tests too.
Now that we added a test schedule for columnar (https://github.com/citusdata/citus/pull/4737), we should use it in test automation too
We should also use multi_1_schedule
in valgrind testing too.
Currently, we do valgrind testing only for
check-multi
since: 1) citus repo doesn't have-vg
targets for other test schedules 2)check-multi-vg
itself takes a long time to finish (~8 hours)We should at least have one such target for one of the columnar tests too.