Re: Added unit test suite for process functions

[Marvin]

Hi,

While running your changed tests on Windows, I think I found new failures.
Being a bot and all I'm not very good at pattern recognition, so I might be
wrong, but could you please double-check?
Full results can be found at
http://testbot.winehq.org/JobDetails.pl?Key=7260

Your paranoid android.


=== W98SE (32 bit process) ===
process.c:59: Test failed: unexpected number of characters: read 0, expected 7
process.c:64: Test failed: unexpected string read: read "", expected "stdout\x0a"
process.c:86: Test failed: unexpected number of characters: read 0, expected 8
process.c:91: Test failed: unexpected string read: read "", expected "stdout\x0d\x0a"
process.c:108: Test failed: _pclose should return after 2 seconds, but it returned after 0 seconds
process.c:119: Test failed: _pclose should return 123, but it returned 0

=== WNT4WSSP6 (32 bit process) ===
process.c:108: Test failed: _pclose should return after 2 seconds, but it returned after 0 seconds
process.c:119: Test failed: _pclose should return 123, but it returned 0

=== W2KPROSP4 (32 bit process) ===
process.c:108: Test failed: _pclose should return after 2 seconds, but it returned after 0 seconds

=== WXPPROSP3 (32 bit process) ===
process.c:108: Test failed: _pclose should return after 2 seconds, but it returned after 0 seconds

=== W2K3R2SESP2 (32 bit process) ===
process.c:108: Test failed: _pclose should return after 2 seconds, but it returned after 0 seconds

=== W7PROX64 (32 bit process) ===
process.c:108: Test failed: _pclose should return after 2 seconds, but it returned after 0 seconds

=== W7PROX64 (64 bit process) ===
process.c:108: Test failed: _pclose should return after 2 seconds, but it returned after 0 seconds