"Rolf Kalbermatter" r.kalbermatter@hccnet.nl wrote:
The test framework should not only help avoiding regressions for the VERY active developers but allow anyone working on Wine in one way or the other to have some confidence that he got it to build right. It's what I usually do when installing any source package to see if I missed something. Getting a long list of errors and sometimes crashes out of the box really leaves a bad taste and also makes it much harder to verify that my own modifications to it later on didn't break it in some ways.
That's the whole reason behind http://wiki.winehq.org/MakeTestFailures
Carefully investigating each test failure one by one as Dan does is the right approach IMO, flaming on wine-devel is not.