Re: Windows build farm failures

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Michael Meskes" <meskes(at)postgresql(dot)org>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Windows build farm failures
Date: 2006-09-25 11:05:32
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D00B@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: Michael Meskes [mailto:meskes(at)postgresql(dot)org]
> Sent: 25 September 2006 11:57
> To: Dave Page
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Windows build farm failures
>
> On Sun, Sep 24, 2006 at 08:54:35PM +0100, Dave Page wrote:
> > Snake and Bandicoot are still hanging in ECPG-Check at the moment.
> > Killing the dt_test.exe program that the regression tests seem to be
> > running frees it all up to properly report the failure. I don't have
> > time to investigate further at the minute, but for anyone that does,
> > Bandicoot's last run was completed only by killing
> dt_test.exe, whereas
> > Snakes was a little more random :-)
>
> I just had a look at the reports and it seems we have several things
> going on:
>
> 1) libpq gives additional information when not able to connect:
> could not connect to server: Connection refused
> (0x0000274D/10061)
> instead of just:
> could not connect to server: Connection refused
>
> Any idea?

Windows error codes I guess.

> 2) Printf "%g" with a double high enough for an exponential
> output gives
> a difference in the exponent. This is due to Windows using three
> digits while the Unixes use just two, e.g. e+027 instead of e+27.
>
> This double stuff creates so many headaches that I wonder if we
> better not test it at all in the regression suite. Comments?
>
> 3) dt_test had to be killed. Judging from the logs it seems
> the program
> hang in either PGTYPESdate_from_asc() or
> PGTYPEStimestamp_from_asc().
> Could someone with a Windows/PostgreSQL setup run this test with
> debugging symbols and tell me where it hangs? It looks like an
> endless loop to me, but apparently nothing happens on other archs.

Unfortunately I'm one of those people who never, ever managed to get a
useful backtrace out of GDB on Windows. The only person I've heard of
who actually managed to do it enough to document it was Merlin.

> 4) snake even stopped building the regression suite:
> testing sql/indicators.pgc ...
> make[1]: *** [check] Error 1
> make[1]: Leaving directory
> `/usr/local/build-farm/HEAD/pgsql.4896/src/interfaces/ecpg/test'
> make: *** [check] Error 2
>
> Was this killed manually too? Or did it stop on its own? I'm
> surprised there is no output explaning why it stops.

It was killed, but I started with some of the sh.exe's before I saw that
dt_test.exe was running. I've just killed dt_test.exe (and nothing else)
on Snake and Bandicoot, so you should see a new set of results for both.

Regards, Dave.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gurjeet Singh 2006-09-25 11:14:47 Broken link in PG docs
Previous Message Michael Meskes 2006-09-25 10:57:20 Re: Windows build farm failures