external
/
citus
mirror of https://github.com/citusdata/citus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Check tests more for flakyness

enable-progress-monitor-isolation-tests-again-flaky2
Jelte Fennema 2022-10-10 10:59:44 +02:00
parent 9b2fcd0b69
commit 5d67f3e38b
2 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.circleci/config.yml
View File

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

6
src/test/regress/spec/isolation_shard_rebalancer_progress.spec
View File

@ -1,8 +1,4 @@
setup setup
{
CALL citus_cleanup_orphaned_shards();
}
setup
{ {
ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 1500001; ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 1500001;
SET citus.shard_count TO 4; 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 // 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 // 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 // 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" step "s4-shard-move-sep-block-writes-without-advisory-locks"
{ {
BEGIN; BEGIN;