"make check" changes have caused buildfarm deterioration.

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема "make check" changes have caused buildfarm deterioration.
Дата
Msg-id 55AD5F41.10601@pgexperts.com
обсуждение исходный текст
Ответы Re: "make check" changes have caused buildfarm deterioration.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Somewhere along the way some changes to the way we do "make check" have 
caused a significant deterioration in the buildfarm's logging. Compare 
these two from animal crake, which happens to be my test instance: 
<http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=crake&dt=2015-07-20%2013%3A09%3A02&stg=check> 
and 
<http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=crake&dt=2015-07-20%2017%3A23%3A08&stg=check> 


In the first place, we now have all that extraneous installation logging 
at the top, and the stuff we are most likely to be interested in right 
at the bottom. But more importantly, we are now missing the initdb log 
and the postmaster log, and the function to get a stack trace if 
required is almost certainly going to be broken as well.

What's most annoying is that some of the  stuff for this hasn't just 
moved, but some is now apparently now cleaned up and removed so the 
buildfarm script can't get at it at all.

I'm going to look at what can be done to repair the damage. No doubt I 
should have been paying more attention, but sometimes I just can't keep 
track of everything going on. Fixing this will almost certainly involve 
some core changes, though.

Incidentally, this has real consequences: I just went looking to find 
the postmaster log of a case that had an error and it was missing - 
that's how I noticed this.

cheers

andrew



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: All-zero page in GIN index causes assertion failure
Следующее
От: Adam Brightwell
Дата:
Сообщение: Unnecessary #include in objectaddress.h?