Re: spoonbill vs. -HEAD

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgresql Hackers Mailinglist <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: spoonbill vs. -HEAD
Date: 2013-03-26 19:59:23
Message-ID: 5151FE1B.7040505@kaltenbrunner.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/26/2013 08:45 PM, Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> I finally started to investigate why spoonbill stopped reporting to the
>> buildfarm feedback about 2 months ago.
>> It seems that the foreign-keys locking patch (or something commity very
>> close to January 23th) broke it in a fairly annoying way - running the
>> buildfarm script seems to
>> consistently "stall" during the isolationtester part of the regression
>> testing leaving the postgresql instance running causing all future
>> buildfarm runs to fail...
>
> It looks from here like the isolationtester client is what's dropping
> the ball --- the backend states are unsurprising, and two of them are
> waiting for a new client command. Can you get a stack trace from the
> isolationtester process?

https://www.kaltenbrunner.cc/files/isolationtester.txt

Stefan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2013-03-26 20:14:53 Re: [COMMITTERS] pgsql: Add PF_PRINTF_ATTRIBUTE to on_exit_msg_fmt.
Previous Message Alvaro Herrera 2013-03-26 19:49:59 Re: sql_drop Event Triggerg