Re: [Pgbuildfarm-members] [Fwd: RE: Build farm on Windows] - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: [Pgbuildfarm-members] [Fwd: RE: Build farm on Windows]
Date
Msg-id 44C9FBFC.1000603@dunslane.net
Whole thread Raw
In response to [Fwd: RE: Build farm on Windows]  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: [Pgbuildfarm-members] [Fwd: RE: Build farm on Windows]  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
The TimeZone changes are looking might suspicious ...

cheers

andrew

Stefan Kaltenbrunner wrote:
> Andrew Dunstan wrote:
>   
>> Can one of the Windows buildfarm owners please try building and running 
>> "make check" by hand rather than using the buildfarm script? It looks 
>> like they all stopped reporting around the same time, and this might 
>> give us a better clue about when things fall over.
>>
>> Also, if you're up for it, please try reversing this patch, which looks 
>> innocuous enough, but is the only thing I can see in the relevant time 
>> period that looks at all suspicious: 
>> http://archives.postgresql.org/pgsql-committers/2006-07/msg00256.php
>>     
>
>
> looks like the postmaster fails to startup up:
>
> ./pg_regress --temp-install=./tmp_check --top-builddir=../../..
> --temp-port=55678 --schedule=./parallel_schedule --multibyte=SQL_ASCII
> --load-language=plpgsql
> ============== removing existing temp installation    ==============
> ============== creating temporary installation        ==============
> ============== initializing database system           ==============
> ============== starting postmaster                    ==============
>
> pg_regress: postmaster did not start within 60 seconds
> Examine ./log/postmaster.log for the reason
> make[2]: *** [check] Error 2
> make[2]: Leaving directory
> `/home/pgbuild/pgfarmbuild/HEAD/pgsql.1436/src/test/regress'
> make[1]: *** [check] Error 2
> make[1]: Leaving directory
> `/home/pgbuild/pgfarmbuild/HEAD/pgsql.1436/src/test'
> make: *** [check] Error 2
>
>
>
> and the logfile is full of:
>
>
> FATAL:  failed to initialize timezone_abbreviations to "Default"
> FATAL:  failed to initialize timezone_abbreviations to "Default"
> LOG:  background writer process (PID 1568) exited with exit code 0
> LOG:  terminating any other active server processes
> FATAL:  failed to initialize timezone_abbreviations to "Default"
> LOG:  all server processes terminated; reinitializing
> FATAL:  failed to initialize timezone_abbreviations to "Default"
> FATAL:  failed to initialize timezone_abbreviations to "Default"
> LOG:  background writer process (PID 244) exited with exit code 0
> LOG:  terminating any other active server processes
> LOG:  all server processes terminated; reinitializing
> FATAL:  failed to initialize timezone_abbreviations to "Default"
> FATAL:  failed to initialize timezone_abbreviations to "Default"
> LOG:  background writer process (PID 468) exited with exit code 0
> LOG:  terminating any other active server processes
>
> ...
>
>
> Stefan
>
>   



pgsql-hackers by date:

Previous
From: Paul Silveira
Date:
Subject: Re: Better name/syntax for "online" index creation
Next
From: Tom Lane
Date:
Subject: Re: [PATCHES] putting CHECK_FOR_INTERRUPTS in qsort_comparetup()