Skip site navigation (1) Skip section navigation (2)

Re: 'CVS-Unknown' buildfarm failures?

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>,<tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 'CVS-Unknown' buildfarm failures?
Date: 2006-06-02 09:45:16
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40138867B@ratbert.vale-housing.co.uk (view raw or flat)
Thread:
Lists: pgsql-hackers
 

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org 
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of 
> Andrew Dunstan
> Sent: 02 June 2006 03:31
> To: tgl(at)sss(dot)pgh(dot)pa(dot)us
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] 'CVS-Unknown' buildfarm failures?
> 
> cvs-unknown means there are unknown files in the repo:
> 
>    my $unknown_files = grep {/^\?/ } @cvslog;
> ...
>    send_result('CVS-Unknown',$unknown_files,\(at)cvslog)
>      if ($unknown_files);
> 
> This is almost always a case of operator error. buildfarm 
> only ever builds
> in a copy of the repo, not in the permanent repo itself, so 
> there should
> NEVER be any file there which does not come from CVS. I have 
> repeatedly
> advised buildfarm member owners not to build by hand in the 
> buildfarm repos.
>  Not everybody listens, apparently.

The owner of snake can guarantee that that is not the case - that box is
not used for *anything* other than the buildfarm and hasn't even been
logged into for weeks, if not months.

The failures come and go, so I have to suspect something other than
operator error.

Regards, Dave

Responses

pgsql-hackers by date

Next:From: Jackie LengDate: 2006-06-02 10:05:28
Subject: Re: pgsql: Fix calculation of plan node extParams to account for the
Previous:From: Larry RosenmanDate: 2006-06-02 09:09:37
Subject: Re: Going for "all green" buildfarm results

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group