Re: kernel32/tests: Remove variable len which is not really used from test_CommandLine.

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

Your paranoid android.


=== W98SE (32 bit process) ===
Failure running script in VM: Exceeded timeout limit of 315 sec

kernel32/tests: Remove variable len which is not really used from test_CommandLine.

[Gerald Pfeifer]

On Wed, 5 May 2010, testbot(a)testbot.winehq.org 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=1901
>
> Your paranoid android.
>
> === W98SE (32 bit process) ===
> Failure running script in VM: Exceeded timeout limit of 315 sec

There is really no way this patch can have caused this test failure.
So, I double-checked. :-) 

What is the proper way to remark such a false positive?  Follow up
here, on wine-devel as I am doing now?  Retrigger the test somehow?

Gerald

PS: I'm sorry if I missed something on the Wiki, I did check for it.