-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 10/6/2008 11:21 PM: > Oh well. Can we work around it for now by detecting the Cygwin failure > easily (thus disabling parallel tests there)?
I'll see what I can come up with. And meanwhile, I'll be reporting this to the cygwin developers; they value Linux compatibility enough that they might be able to hack this to work after all. > >> As a result, the parallel tests invariably fail: > >> +./micro-suite: line 1703: read: read error: 0: Communication error on send > > Interesting, it didn't do that when I tested it (quite a while ago). Well, my test was on cygwin 1.7.0 (as-yet-unreleased CVS version), rather than 1.5.25, and pipe handling code has changed in the meantime. I need to repeat the tests on 1.5.25, before claiming that this is the definitive failure pattern. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjsEvAACgkQ84KuGfSFAYDAhgCgmi8SKwVj0jY4BYCzuSQMwfzj 30AAoKRF8CprWC/fNeavlAh733HTSmvl =aluX -----END PGP SIGNATURE-----
