Re: PGBuildfarm member narwhal Branch HEAD Status changed from OK to Check failure

From: Dave Page <dpage(at)postgresql(dot)org>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: PGBuildfarm member narwhal Branch HEAD Status changed from OK to Check failure
Date: 2007-05-03 07:36:06
Message-ID: 463990E6.5060206@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

For info, the buildfarm script failed to leave the broken tree behind
again so I was unable to get a dump from the affected index.

Andrew; My run logs show that the script did think it was leaving the
tree behind (it included the 'leaving error trees' text that you asked
me to add to the script). I'm assuming it does leave the tree under the
buildroot for the branch and doesn't try to copy them into /tmp or
somewhere?

Regards, Dave

PG Build Farm wrote:
> The PGBuildfarm member narwhal had the following event on branch HEAD:
>
> Status changed from OK to Check failure
>
> The snapshot timestamp for the build that triggered this notification is: 2007-05-02 20:00:01
>
> The specs of this machine are:
> OS: Windows Server 2003 R2 / 5.2.3790
> Arch: i686
> Comp: GCC / 3.4.2 (mingw-special)
>
> For more information, see http://www.pgbuildfarm.org/cgi-bin/show_history.pl?nm=narwhal&br=HEAD

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-05-03 08:25:29 Re: Sequential scans
Previous Message Simon Riggs 2007-05-03 07:01:32 Re: Sequential scans