"Alex Arazi" alexarazi@gmail.com wrote:
This is a two part patch. The first part is status_reorganization.patch which divides the test routine into function calls. The second part is status_messages.patch which adds message sequencing.
Are you guys planning to monitor test.winehq.org and fix all the failures caused by new message tests?
On 3/14/07, Dmitry Timoshkov dmitry@codeweavers.com wrote:
"Alex Arazi" alexarazi@gmail.com wrote:
This is a two part patch. The first part is status_reorganization.patch which divides the test routine into function calls. The second part is status_messages.patch which adds message sequencing.
Are you guys planning to monitor test.winehq.org and fix all the failures caused by new message tests?
-- Dmitry.
That's a good question. The class the students are taking will be over by the end of next week. I've tried to help them get it right the first time by running their tests on several different Windows platforms and making sure the tests pass on all of them.
BTW, are we evert going to put up a better fron page for test.winehq.org? It still says 403 Forbidden.
- Lei
"Lei Zhang" thestig@google.com wrote:
That's a good question. The class the students are taking will be over by the end of next week. I've tried to help them get it right the first time by running their tests on several different Windows platforms and making sure the tests pass on all of them.
To my experience there are always windows configurations that cause the failures I haven't seen. Since I have written many user32 message tests I regularly go to test.winehq.org and try to fix the failures in my tests.
BTW, are we evert going to put up a better fron page for test.winehq.org? It still says 403 Forbidden.
Just go to directly to test.winehq.org/data.
On Mi, 2007-03-14 at 09:07 -0700, Lei Zhang wrote:
BTW, are we evert going to put up a better front page for test.winehq.org?
It still says 403 Forbidden.
Yes Please: http://bugs.winehq.org/show_bug.cgi?id=3187