Just released a new version of winrash. I'm sending this email because after asking people who are running Winrash to send an email to the list or myself , I didn't receive any emails. This isn't usually a problem except when there is an issue with Winrash. I get error reports that have the IDs people put in but no way to contact them.
So I added a field in the installer for a contact email. This will be sent along with the clientID when an error report is generated by winrash.
In case anyone is curious the web archive for the error reports is here: http://www.winehq.org/hypermail/wine-tests-results/
I'd like to ask that anyone who installed winrash please run the installer again so they can enter a valid contact email. If you are one of those people wondering why your results aren't found at http://test.winehq.org/data/ this will help both of us by letting me get a hold of you ;-)
The one change I should mention is the addition of proxy support in the 0008 release. There are a handful of people running behind proxies, I can tell by squid html in what should be the script part of the error reports. This version of the client *should* fix things for you. Thanks to Florian Steinel for the code change.
Here is the SF link to the latest client: http://osdn.dl.sourceforge.net/sourceforge/winrash/winrash-0008-chris-msvc.e...
Thanks to anyone running the testing suite and for the feedback on winrash changes, I appreciate it.
Thanks, Chris
On Wed, 09 Jun 2004 22:23:07 -0400, Chris Morgan wrote:
In case anyone is curious the web archive for the error reports is here: http://www.winehq.org/hypermail/wine-tests-results/
Most of those emails seem to have no data in them?
Winrash version: 4378004 ClientID: Operating system: dwMajorVersion=4 dwMinorVersion=10 dwBuildNumber=67766446 PlatformId=1 szCSDVersion= A wServicePackMajor=0 wServicePackMinor=0 wProductType=6745844 wReserved=6747024 Cookies: winetest = winetest-200406051000-paul-mingw.zip winetest_history = winrash-0007-chris-msvc.exe,winetest-200406031000-paul-mingw.zip,winetest-200406031000-kevin-mingw.exe,winetest-200406041000-kevin-mingw.exe,winetest-200406041000-paul-mingw.zip,winetest-200406041000-paul-mingw.exe,winetest-200406041000-kevin-mingw.zip,winetest-200406051000-kevin-mingw.exe,winetest-200406051000-paul-mingw.exe,winetest-200406051000-kevin-mingw.zip Script: Command in error: 0
What does "command in error" mean? What is this email supposed to tell us?
thanks -mike
This particular error report is quite odd. It's not from version 0008, the latest version, as I fixed the "Winrash version:" to actually print the winrash version, not the decimal value of pointer to the string, heh. There is no script so the client is probably unable to connect to test.winehq.org and get a script from the cgi there. The command in error usually points to the command where the error occurred.
If winrash can't get a script it can't even be told to upgrade itself. Since we have no email or clientID we can't just contact them and get more information. I think we should just block every error report with a null or the old default "WinrashDefaultID" or these may continue for some time.
Chris
On Friday 11 June 2004 2:11 pm, Mike Hearn wrote:
On Wed, 09 Jun 2004 22:23:07 -0400, Chris Morgan wrote:
In case anyone is curious the web archive for the error reports is here: http://www.winehq.org/hypermail/wine-tests-results/
Most of those emails seem to have no data in them?
Winrash version: 4378004 ClientID: Operating system: dwMajorVersion=4 dwMinorVersion=10 dwBuildNumber=67766446 PlatformId=1 szCSDVersion= A wServicePackMajor=0 wServicePackMinor=0 wProductType=6745844 wReserved=6747024 Cookies: winetest = winetest-200406051000-paul-mingw.zip winetest_history = winrash-0007-chris-msvc.exe,winetest-200406031000-paul-mingw.zip,winetest-2 00406031000-kevin-mingw.exe,winetest-200406041000-kevin-mingw.exe,winetest-2 00406041000-paul-mingw.zip,winetest-200406041000-paul-mingw.exe,winetest-200 406041000-kevin-mingw.zip,winetest-200406051000-kevin-mingw.exe,winetest-200 406051000-paul-mingw.exe,winetest-200406051000-kevin-mingw.zip Script: Command in error: 0
What does "command in error" mean? What is this email supposed to tell us?
thanks -mike
-
Chris Morgan -
Mike Hearn