Re: kernel32/tests: Remove variable ret which is not really used from load_blackbox. (RESEND)

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=1969

Your paranoid android.

=== W7PROX64 (64 bit debugger) ===
debugger.c:299: Test failed: Timed out waiting for the child to crash
debugger.c:313: Test failed: wrong exit code : 00000103
debugger.c:324: Test failed: Timed out waiting for the debugger
debugger.c:146: Test failed: wrong size for 'C:\Users\winetest\AppData\Local\Temp\wt5825.tmp': read=0
debugger.c:329: Test failed: wrong debugger argument count: -28562032
debugger.c:330: Test failed: the child and debugged pids don't match: 660 != 2046
debugger.c:299: Test failed: Timed out waiting for the child to crash
debugger.c:306: Test failed: wrong exit code : 00000103
debugger.c:324: Test failed: Timed out waiting for the debugger
debugger.c:146: Test failed: wrong size for 'C:\Users\winetest\AppData\Local\Temp\wt2D25.tmp': read=0
debugger.c:329: Test failed: wrong debugger argument count: -28562032
debugger.c:330: Test failed: the child and debugged pids don't match: 1368 != 2046
Timeout

kernel32/tests: Remove variable ret which is not really used from load_blackbox. (RESEND)

[Gerald Pfeifer]

On Sun, 9 May 2010, [e-mail] wrote:
> 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=1969

I did double check, and this is a false positive.  This failure is
not (and really cannot) be caused by my patch.

Is the patch acceptable with that in mind?

Gerald