Re: regression failures - further data

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: regression failures - further data
Date: 2004-05-07 15:31:53
Message-ID: 409BABE9.7080808@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32

Andrew Dunstan wrote:

>
> still investigating ...
>

The log traces (log_connections=true, log_disconnections=true,
log_statement='all') show that if I run without limiting
max_connections, the next tests start up before the copy is finished -
no wonder things get right royally screwed as a result.

It seems like the problem is in the Msys shell. It appears not to wait
correctly for a job to finish (Single tests are run in the foreground by
the shell, so no explicit 'wait' is run - I tried putting one in with no
effect). It's probably triggered by the copy test because it takes such
a long time. I have no idea why the parallelism of the tests should
affect it.

trying to find a workaround.

Does anyone have any contacts with the MINGW/MSys people?

cheers

andrew

In response to

Responses

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Hisaji ONO 2004-05-07 15:48:10 Couldn't make check
Previous Message Andrew Dunstan 2004-05-07 14:20:53 Re: regression failures - further data