Check tests more for flakyness

.circleci/config.yml

@@ -539,7 +539,7 @@ jobs:
 
   test-flakyness:
     description: Runs a test multiple times to see if it's flaky
-    parallelism: 32
+    parallelism: 64
     parameters:
       pg_major:
         description: 'postgres major version'
@@ -561,7 +561,7 @@ jobs:
       runs:
         description: 'number of times that the test should be run in total'
         type: integer
-        default: 1600
+        default: 2400
     docker:
       - image: '<< parameters.image >>:<< parameters.image_tag >><< pipeline.parameters.image_suffix >>'
     working_directory: /home/circleci/project

src/test/regress/spec/isolation_shard_rebalancer_progress.spec

@@ -1,8 +1,4 @@
 setup
-{
-	CALL citus_cleanup_orphaned_shards();
-}
-setup
 {
 	ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 1500001;
 	SET citus.shard_count TO 4;
@@ -105,7 +101,7 @@ step "s4-shard-move-sep-block-writes"
 // Running two shard moves at the same time can cause racy behaviour over who
 // gets the lock. For the test where this move is used in we don't rely on the
 // advisory locks. So we disable taking the advisory lock there to avoid the
-// racy lock acquisition with the other concurretn move.
+// racy lock acquisition with the other concurrent move.
 step "s4-shard-move-sep-block-writes-without-advisory-locks"
 {
 	BEGIN;