Move test in isolation schedule to prevent failure

We check for metadata consistency across the cluster in the test
isolation_metadata_sync_vs_all. However, some earlier tests in
enterprise repo leave invalid pg_dist_node entries in the worker nodes
that have Oid values for already dropped role objects.

To remedy that, I suggest that we move the test to earlier in the
schedule, thereby making the tests pass for the time being. We should
later introduce metadata checking either in a new isolation test or by
moving this test later in the schedule. However, we should do that after
we fix the underlying issue.
pull/5718/head
Hanefi Onaldi 2022-02-17 06:16:51 +03:00
parent 57319b23d0
commit ccc4cc6bf0
No known key found for this signature in database
GPG Key ID: F18CDB10BA0DFDC7
1 changed files with 1 additions and 1 deletions

View File

@ -19,6 +19,7 @@ test: isolation_cluster_management
# the following tests depend on the distributed # the following tests depend on the distributed
# transactionId, so should not be parallelized # transactionId, so should not be parallelized
# and no tests should be added before these # and no tests should be added before these
test: isolation_metadata_sync_vs_all
test: isolation_distributed_transaction_id test: isolation_distributed_transaction_id
test: isolation_dump_global_wait_edges test: isolation_dump_global_wait_edges
test: isolation_citus_dist_activity test: isolation_citus_dist_activity
@ -92,7 +93,6 @@ test: isolation_metadata_sync_deadlock
test: isolation_replicated_dist_on_mx test: isolation_replicated_dist_on_mx
test: isolation_replicate_reference_tables_to_coordinator test: isolation_replicate_reference_tables_to_coordinator
test: isolation_multiuser_locking test: isolation_multiuser_locking
test: isolation_metadata_sync_vs_all
# MXless tests # MXless tests
test: isolation_check_mx test: isolation_check_mx