Re: Recent failures in IsolationCheck deadlock-hard

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Recent failures in IsolationCheck deadlock-hard
Date: 2019-08-06 06:06:56
Message-ID: CA+hUKGJRHCnA8ArQx0MpwnX49-Y_d6uP-6YX9bKMZk3CoKHi8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Aug 3, 2019 at 2:11 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> > There have been five failures on three animals like this, over the
> > past couple of months:
>
> Also worth noting is that anole failed its first try at the new
> deadlock-parallel isolation test:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2019-08-01%2015%3A48%3A16

And friarbird (also CLOBBER_CACHE_ALWAYS) fails every time.

animal | snapshot | branch | commit | result |
fail_stage | fail_tests
-----------+---------------------+--------+---------+---------+----------------+---------------------
lousyjack | 2019-08-05 11:33:02 | HEAD | a76cfba | FAILURE |
IsolationCheck | {deadlock-parallel}
gharial | 2019-08-05 10:30:37 | HEAD | a76cfba | FAILURE |
IsolationCheck | {deadlock-parallel}
friarbird | 2019-08-05 05:20:01 | HEAD | 8548ddc | FAILURE |
IsolationCheck | {deadlock-parallel}
friarbird | 2019-08-04 05:20:02 | HEAD | 69edf4f | FAILURE |
IsolationCheck | {deadlock-parallel}
hyrax | 2019-08-03 12:20:57 | HEAD | 2abd7ae | FAILURE |
IsolationCheck | {deadlock-parallel}
friarbird | 2019-08-03 05:20:01 | HEAD | 2abd7ae | FAILURE |
IsolationCheck | {deadlock-parallel}
friarbird | 2019-08-02 05:20:00 | HEAD | a9f301d | FAILURE |
IsolationCheck | {deadlock-parallel}
anole | 2019-08-01 15:48:16 | HEAD | da9456d | FAILURE |
IsolationCheck | {deadlock-parallel}

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=lousyjack&dt=2019-08-05%2011:33:02
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=gharial&dt=2019-08-05%2010:30:37
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=friarbird&dt=2019-08-05%2005:20:01
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=friarbird&dt=2019-08-04%2005:20:02
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hyrax&dt=2019-08-03%2012:20:57
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=friarbird&dt=2019-08-03%2005:20:01
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=friarbird&dt=2019-08-02%2005:20:00
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=anole&dt=2019-08-01%2015:48:16

1
step d2a1: <... completed>
-sum
-
-10000
+error in steps d1c e1l d2a1: ERROR: canceling statement due to user request
step e1c: COMMIT;
-step d2c: COMMIT;
step e2l: <... completed>
lock_excl

1
+step d2c: COMMIT;
step e2c: COMMIT;

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-08-06 06:13:45 Re: The unused_oids script should have a reminder to use the 8000-8999 OID range
Previous Message Peter Geoghegan 2019-08-06 05:58:26 Re: The unused_oids script should have a reminder to use the 8000-8999 OID range