Re: 'CVS-Unknown' buildfarm failures?
От | Dave Page |
---|---|
Тема | Re: 'CVS-Unknown' buildfarm failures? |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E40138867B@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответы |
Re: 'CVS-Unknown' buildfarm failures?
|
Список | pgsql-hackers |
> -----Original Message----- > From: pgsql-hackers-owner@postgresql.org > [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of > Andrew Dunstan > Sent: 02 June 2006 03:31 > To: tgl@sss.pgh.pa.us > Cc: pgsql-hackers@postgresql.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,\@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
В списке pgsql-hackers по дате отправления: