mirror of https://github.com/citusdata/citus.git
disable one of deadlock detection test (#3682)
It seems that one of the deadlock detection tests fails way too often in our CI. The difference is only ordering. Currently it seems that it is a good idea to disable this test for the sake of development.pull/3679/head
parent
6cd32b0db1
commit
5bf9f32dd3
|
@ -246,41 +246,6 @@ step s2-commit:
|
||||||
COMMIT;
|
COMMIT;
|
||||||
|
|
||||||
|
|
||||||
starting permutation: s1-begin s2-begin s2-insert-ref-10 s1-insert-ref-11 s2-insert-ref-11 s1-insert-ref-10 deadlock-checker-call s1-commit s2-commit
|
|
||||||
step s1-begin:
|
|
||||||
BEGIN;
|
|
||||||
|
|
||||||
step s2-begin:
|
|
||||||
BEGIN;
|
|
||||||
|
|
||||||
step s2-insert-ref-10:
|
|
||||||
INSERT INTO deadlock_detection_reference VALUES (10, 10);
|
|
||||||
|
|
||||||
step s1-insert-ref-11:
|
|
||||||
INSERT INTO deadlock_detection_reference VALUES (11, 11);
|
|
||||||
|
|
||||||
step s2-insert-ref-11:
|
|
||||||
INSERT INTO deadlock_detection_reference VALUES (11, 11);
|
|
||||||
<waiting ...>
|
|
||||||
step s1-insert-ref-10:
|
|
||||||
INSERT INTO deadlock_detection_reference VALUES (10, 10);
|
|
||||||
<waiting ...>
|
|
||||||
step deadlock-checker-call:
|
|
||||||
SELECT check_distributed_deadlocks();
|
|
||||||
|
|
||||||
check_distributed_deadlocks
|
|
||||||
|
|
||||||
t
|
|
||||||
step s2-insert-ref-11: <... completed>
|
|
||||||
step s1-insert-ref-10: <... completed>
|
|
||||||
error in steps deadlock-checker-call s2-insert-ref-11 s1-insert-ref-10: ERROR: canceling the transaction since it was involved in a distributed deadlock
|
|
||||||
step s1-commit:
|
|
||||||
COMMIT;
|
|
||||||
|
|
||||||
step s2-commit:
|
|
||||||
COMMIT;
|
|
||||||
|
|
||||||
|
|
||||||
starting permutation: s1-begin s2-begin s2-insert-ref-10 s1-update-1 deadlock-checker-call s2-update-1 s1-insert-ref-10 deadlock-checker-call s1-commit s2-commit
|
starting permutation: s1-begin s2-begin s2-insert-ref-10 s1-update-1 deadlock-checker-call s2-update-1 s1-insert-ref-10 deadlock-checker-call s1-commit s2-commit
|
||||||
step s1-begin:
|
step s1-begin:
|
||||||
BEGIN;
|
BEGIN;
|
||||||
|
|
|
@ -94,10 +94,10 @@ step s2-view-worker:
|
||||||
|
|
||||||
query query_hostname query_hostport master_query_host_namemaster_query_host_portstate wait_event_typewait_event usename datname
|
query query_hostname query_hostport master_query_host_namemaster_query_host_portstate wait_event_typewait_event usename datname
|
||||||
|
|
||||||
UPDATE public.ref_table_1400163 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)localhost 57638 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
UPDATE public.ref_table_1400154 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)localhost 57638 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
||||||
UPDATE public.ref_table_1400163 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)localhost 57637 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
UPDATE public.ref_table_1400154 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)localhost 57637 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
||||||
UPDATE public.ref_table_1400163 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)coordinator_host57636 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
UPDATE public.ref_table_1400154 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)coordinator_host57636 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
||||||
UPDATE public.ref_table_1400163 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)localhost 57636 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
UPDATE public.ref_table_1400154 ref_table SET a = (a OPERATOR(pg_catalog.+) 1)localhost 57636 coordinator_host57636 idle in transactionClient ClientRead postgres regression
|
||||||
step s2-end:
|
step s2-end:
|
||||||
END;
|
END;
|
||||||
|
|
||||||
|
|
|
@ -398,7 +398,9 @@ permutation "s1-begin" "s2-begin" "s1-update-1" "s2-update-2" "s1-update-2" "dea
|
||||||
permutation "s1-begin" "s2-begin" "s1-insert-dist-10" "s2-insert-local-10" "s2-insert-dist-10" "s1-insert-local-10" "deadlock-checker-call" "s1-commit" "s2-commit"
|
permutation "s1-begin" "s2-begin" "s1-insert-dist-10" "s2-insert-local-10" "s2-insert-dist-10" "s1-insert-local-10" "deadlock-checker-call" "s1-commit" "s2-commit"
|
||||||
|
|
||||||
// daedlock with reference tables only
|
// daedlock with reference tables only
|
||||||
permutation "s1-begin" "s2-begin" "s2-insert-ref-10" "s1-insert-ref-11" "s2-insert-ref-11" "s1-insert-ref-10" "deadlock-checker-call" "s1-commit" "s2-commit"
|
// this test fails way too often in our CI. The failure is order related failure, so disabling it
|
||||||
|
// for now seems a good option.
|
||||||
|
//permutation "s1-begin" "s2-begin" "s2-insert-ref-10" "s1-insert-ref-11" "s2-insert-ref-11" "s1-insert-ref-10" "deadlock-checker-call" "s1-commit" "s2-commit"
|
||||||
|
|
||||||
// deadlock with referecen + distributed tables
|
// deadlock with referecen + distributed tables
|
||||||
permutation "s1-begin" "s2-begin" "s2-insert-ref-10" "s1-update-1" "deadlock-checker-call" "s2-update-1" "s1-insert-ref-10" "deadlock-checker-call" "s1-commit" "s2-commit"
|
permutation "s1-begin" "s2-begin" "s2-insert-ref-10" "s1-update-1" "deadlock-checker-call" "s2-update-1" "s1-insert-ref-10" "deadlock-checker-call" "s1-commit" "s2-commit"
|
||||||
|
|
Loading…
Reference in New Issue