Winrash / Winetest

[Stephen Ogletree]

(I sent a version of this to wine-users originally and Ivan said to send 
it over here to wine-devel)

On windows XP, with the latest patches/service packs, I got the errors 
below.

Since these were popups and/or crashes, I'm assuming they need to be 
reported manually.

0.  Small issue: The winrash installer (NSIS) concludes with a window 
that has 3 lines that are in blue text to suggest a hyperlink (and the 
surrounding text even says "Click the text below to make a bookmark for 
the test results") but clicking the text has no visible effect (when 
moving the cursor over the text, the cursor does change shape to 
indicate the text is clickable, so at least that much works...).   My 
default browser is Opera and my security settings in IE are maxed out, 
with everything possible disabled.  In Opera, I typically keep popups, 
plugins, and javascript disabled, but none of that should keep normal 
URL to a html page from opening.

Since installing winrash didn't do anything except put the service in 
place and start it, I figured I'd go ahead and download the test 
manually.  This rest of this email pertains to 
/winetest-200407091000-kevin-mingw.exe/

1.  I received the "Can't parse subtests output of msvcrtd" message 
during 'extraction'.  I assume this is the same error Holly reported.

2.  I had a message indicating a timeout during the user32 tests (before 
the network tests - this appears to be the same message Holly reported). 
   Also, I remember the timeout was occurring back when we first tried 
out this testing program a month or two (or 3?) ago, so its a bug thats 
been around a while.

3.  I am still seeing an error that I pointed out in the first round (or 
a long time ago, at least..) of testing where the test crashes Explorer 
(this is after the timeout, but before the prompt to send the results). 
  Explorer crashing causes all of my desktop icons to reset to their 
positions from when I last logged in/out (which has been a week or two, 
so this was significant change), as well as causes some of the SysTray 
icons to vanish, and finally, of course I lose the start menu bar and 
the bar containing the running application names for a moment, while 
Windows XP nicely restarts explorer.exe.  Meanwhile, there's no 
indication of trouble from the winetest window.

FWIW: When I agreed to submit my test results, I did *not* receive any 
warning about my log being too big.

Stephen Ogletree

[Ferenc Wagner]

"Stephen Ogletree"  writes:
> (I sent a version of this to wine-users originally and Ivan said to
> send it over here to wine-devel)

Yes, it's better sent here.  Thanks for the report and sorry
for the long delay.  It's still summer...
> - Small issue: The winrash installer (NSIS) concludes with a window
>
> that has 3 lines that are in blue text to suggest a hyperlink [...]

I think the winrash maintainer got the message.
> Since installing winrash didn't do anything except put the service in
> place and start it, I figured I'd go ahead and download the test
> manually.

Well, the service should download and run new tests as they
got published.  Unfortunately there is some error on server
side so it doesn't work as expected.  We will eventually fix
it and you dormant service process will start working in the
background.
> This rest of this email pertains to
> /winetest-200407091000-kevin-mingw.exe/

Running the winetest suite manually present the user some
interaction which is hidden when invoked by the service.
> - I received the "Can't parse subtests output of msvcrtd" message
>
> during 'extraction'.  I assume this is the same error Holly reported.

In your case it probably means that msvcrtd.dll isn't
installed on your system.
> - I had a message indicating a timeout during the user32 tests
>
> (before the network tests - this appears to be the same message Holly
> reported).  Also, I remember the timeout was occurring back when we
> first tried out this testing program a month or two (or 3?) ago, so
> its a bug thats been around a while.

Yes, it's a bug in the user32 input tests, which I haven't
tried to fix yet, but introduced the timeout instead.  Wrong
tests will also emerge in the future, it's better to handle
them than hang with them...
> - I am still seeing an error that I pointed out in the first round
>
> (or a long time ago, at least..) of testing where the test crashes
> Explorer

That was a deliberate kill, not a crash.  It's excluded now
as far as I know.
> FWIW: When I agreed to submit my test results, I did *not* receive any
> warning about my log being too big.

That warning was removed, we silently truncate now... :)