Winetest: outstanding issues (SERVING)

[Brian Vincent]

As it was written in the Book of Jakob Eriksson <jakov at vmlinux.org>:
> I don't understand any of this and it worries me.

It's ok, really ;)

> Do you mean separate tests, like "kernel32_crosstest.exe", or do you mean
> "winetest.exe"?

The two examples I listed are the only two things we support right now, 
Chris can update his winrash clients automagically (we've actually
had this functionality from the beginning, this was a small tweak.)

What the changes really boil down to is this..

Paul is doing winetest.exe builds that can be hooked into his Wine 
Regression Testing framework.  That means we get builds triggered
2 - 5 times a day as Alexandre does batches of commits.

Kevin is doing winetest.exe builds at some set time each day (4am EST or 
some such.)  These provide a baseline for Paul's.  If something breaks
at this level we can look at Paul's results for more granularity.

The changes today will always distribute the newest winetest.exe to
the winrash clients.  I think we're all on the same page here about
that.  

Dimi - when we get Kevin's builds available and we verify error
reporting is working, let's try to get a good test of everything 
done.  It would be nice to get this done by Sunday.

-Brian