Re: Buildfarm alarms - Mailing list pgsql-hackers

From Dave Page
Subject Re: Buildfarm alarms
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D015@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Re: Buildfarm alarms  (Joachim Wieland <joe@mcknight.de>)
Responses Re: Buildfarm alarms  (Joachim Wieland <joe@mcknight.de>)
List pgsql-hackers

> -----Original Message-----
> From: Joachim Wieland [mailto:joe@mcknight.de]
> Sent: 25 September 2006 13:25
> To: Dave Page
> Cc: Andrew Dunstan; pgsql-hackers@postgresql.org;
> meskes@postgresql.org
> Subject: Re: [HACKERS] Buildfarm alarms
>
> On Sun, Sep 24, 2006 at 11:51:49AM +0100, Dave Page wrote:
> > wrong to the monitoring processes - what had happened was
> that both had
> > hung or got in an inifinite loop in ECPG-check, the machine
> was running
> > just fine
>
> Is this still an issue? Can you provide more information?
> What happens if you
> run ecpg-check manually? Which test hangs?

Dt_test is the one that hangs - though in actual fact what is happening
is that it's crashing and popping up a 'do you wanna debug' dialogue
which doesn't get seen in a non-interactive buildfarm run. After saying
no to that, the complete list of failed tests is (see Snake/Bandicoot's
logs for more info):

testing connect/test1.pgc                      ... FAILED (log)
testing compat_informix/dec_test.pgc           ... FAILED (output)
testing preproc/variable.pgc                   ... FAILED (log, output)
testing pgtypeslib/dt_test.pgc                 ... FAILED (log, output)
testing pgtypeslib/num_test.pgc                ... FAILED (output)
testing pgtypeslib/num_test2.pgc               ... FAILED (output)

Regards, Dave.


pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: DROP FUNCTION IF EXISTS
Next
From: Teodor Sigaev
Date:
Subject: Re: DROP FUNCTION IF EXISTS