Re: regression failures - further data - Mailing list pgsql-hackers-win32

From Andrew Dunstan
Subject Re: regression failures - further data
Date
Msg-id 409BABE9.7080808@dunslane.net
Whole thread Raw
In response to Re: regression failures - further data  (Andrew Dunstan <andrew@dunslane.net>)
Responses white smoke up the chimney
List 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

pgsql-hackers-win32 by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: regression failures - further data
Next
From: "Hisaji ONO"
Date:
Subject: Couldn't make check