From 3b7959a763d062c761577c5e81950f6474405805 Mon Sep 17 00:00:00 2001 From: SaitTalhaNisanci Date: Mon, 23 Mar 2020 14:38:18 +0300 Subject: [PATCH] not run local shard copy test in parallel (#3640) It seems that when logging is enabled we should not run local shard copy in parallel with other tests. The reason is that it adds coordinator for reference tables and if the parallel test creates a schema before this test is run, the schema will be logged. So it is not deterministic. --- src/test/regress/multi_mx_schedule | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/test/regress/multi_mx_schedule b/src/test/regress/multi_mx_schedule index dda14a23d..0e6a38a69 100644 --- a/src/test/regress/multi_mx_schedule +++ b/src/test/regress/multi_mx_schedule @@ -40,12 +40,13 @@ test: master_evaluation master_evaluation_modify master_evaluation_select test: multi_mx_call test: multi_mx_function_call_delegation test: multi_mx_modifications local_shard_execution +test: local_shard_copy test: multi_mx_transaction_recovery test: multi_mx_modifying_xacts test: multi_mx_explain test: multi_mx_reference_table test: multi_mx_insert_select_repartition -test: locally_execute_intermediate_results local_shard_copy +test: locally_execute_intermediate_results # test that no tests leaked intermediate results. This should always be last test: ensure_no_intermediate_data_leak