[Fwd: PGBuildfarm member narwhal Branch HEAD Status changed from OK to InstallCheck failure]

Started by Dave Pageover 18 years ago3 messages
#1Dave Page
dpage@postgresql.org

This was another occurance of the strange create index failure on
Narwhal - unfortunately, despite having 'keep_error_builds' => 1 in my
BF config it seems to have removed the tree so I can't get the dump that
Tom wanted.

Does anyone know why the keep_error_builds option didn't work in this
case? Or have I misinterpreted it's meaning?

Regards, Dave.

-------- Original Message --------
Subject: PGBuildfarm member narwhal Branch HEAD Status changed from OK
to InstallCheck failure
Date: Wed, 25 Apr 2007 19:34:34 -0700 (PDT)
From: PG Build Farm <pgbuildfarm-web@hosting-two.commandprompt.com>
To: pgbuildfarm-status-chngs@pgfoundry.org,
pgbuildfarm-status-green@pgfoundry.org

The PGBuildfarm member narwhal had the following event on branch HEAD:

Status changed from OK to InstallCheck failure

The snapshot timestamp for the build that triggered this notification
is: 2007-04-26 02: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&amp;br=HEAD

#2Andrew Dunstan
andrew@dunslane.net
In reply to: Dave Page (#1)
Re: [Pgbuildfarm-members] [Fwd: PGBuildfarm member narwhal Branch HEAD Status changed from OK to InstallCheck failure]

Dave Page wrote:

This was another occurance of the strange create index failure on
Narwhal - unfortunately, despite having 'keep_error_builds' => 1 in my
BF config it seems to have removed the tree so I can't get the dump that
Tom wanted.

Does anyone know why the keep_error_builds option didn't work in this
case? Or have I misinterpreted it's meaning?

Well, "anyone" will usually be me ;-)

To the best of my knowledge and belief it does work. This is the code it
should cause to be executed:

my $timestr = strftime "%Y-%m-%d-%H:%M:%S", localtime($now);
move("$pgsql", "pgsqlkeep.$timestr");
move("inst", "instkeep.$timestr") if (-d "inst") ;

Please see if you can trap the script stdout/stderr somewhere so that next
time it fails you can send it to me.

How exactly do you have the buildfarm runs automated? Maybe that does a
little cleaning of its own?

cheers

andrew

#3Dave Page
dpage@postgresql.org
In reply to: Andrew Dunstan (#2)
Re: [Pgbuildfarm-members] [Fwd: PGBuildfarm member narwhal Branch HEAD Status changed from OK to InstallCheck failure]

Andrew Dunstan wrote:

Dave Page wrote:

This was another occurance of the strange create index failure on
Narwhal - unfortunately, despite having 'keep_error_builds' => 1 in my
BF config it seems to have removed the tree so I can't get the dump that
Tom wanted.

Does anyone know why the keep_error_builds option didn't work in this
case? Or have I misinterpreted it's meaning?

Well, "anyone" will usually be me ;-)

Yeah, I know but I didn't want to presume :-)

To the best of my knowledge and belief it does work. This is the code it
should cause to be executed:

my $timestr = strftime "%Y-%m-%d-%H:%M:%S", localtime($now);
move("$pgsql", "pgsqlkeep.$timestr");
move("inst", "instkeep.$timestr") if (-d "inst") ;

Please see if you can trap the script stdout/stderr somewhere so that next
time it fails you can send it to me.

I already log the run output - there's nothing unusual in there.

How exactly do you have the buildfarm runs automated? Maybe that does a
little cleaning of its own?

A simple batch script, run from the task scheduler which fires off the
script. It doesn't do any cleanup at all.

Regards, Dave.