I have been working on enabling the remaining TAP tests on MSVC build in the buildfarm client, but I have come across an odd problem. The bin tests all run fine, but the recover tests crash and in such a way as to crash the buildfarm client itself and require some manual cleanup. This happens at some stage after the tests have run (the final "ok" is output) but before the END handler in PostgresNode.pm (I put some traces in there to see if I could narrow down where there were problems).
The symptom is that this appears at the end of the output when the client calls "vcregress.pl taptest src/test/recover":
Terminating on signal SIGBREAK(21) Terminating on signal SIGBREAK(21) Terminate batch job (Y/N)?
And at that point there is nothing at all apparently running, according to Sysinternals Process Explorer, including the buildfarm client.
It's 100% repeatable on bowerbird, and I'm a bit puzzled about how to fix it.
Anyone have any clues?
That looks like we've upset CMD.exe its self. I'm not sure how ... leaking a signal to the parent proc?
I suspect this could be something to do with console process groups.
Bowerbird is win8 . So this isn't going to be related to the support for ANSI escapes added in win10.
A serach for the error turns up a complaint about IPC::Run as the first hit. Probably not coincidence.
