We've had a test suite for six or so years now, and we keep getting closer to having it pass reliably, but we're still not quite there. I see from http://test.winehq.org that fifteen tests fail on at least one machine.
There are several bugs that only cause make test to fail if you run them with WINEDEBUG=warn+heap, but those seem just as important to me.
On my own machine, here are the bugs related to make test failures: http://bugs.winehq.org/show_bug.cgi?id=12925 http://bugs.winehq.org/show_bug.cgi?id=14078 http://bugs.winehq.org/show_bug.cgi?id=17414 http://bugs.winehq.org/show_bug.cgi?id=17518 http://bugs.winehq.org/show_bug.cgi?id=19183
I submitted a patch to fix http://bugs.winehq.org/show_bug.cgi?id=17518 but it'd be nice to get some love on the others. - Dan
On Sat, Jul 4, 2009 at 10:48 AM, Dan Kegeldank@kegel.com wrote:
We've had a test suite for six or so years now, and we keep getting closer to having it pass reliably, but we're still not quite there. I see from http://test.winehq.org that fifteen tests fail on at least one machine.
There are several bugs that only cause make test to fail if you run them with WINEDEBUG=warn+heap, but those seem just as important to me.
On my own machine, here are the bugs related to make test failures: http://bugs.winehq.org/show_bug.cgi?id=12925 http://bugs.winehq.org/show_bug.cgi?id=14078 http://bugs.winehq.org/show_bug.cgi?id=17414 http://bugs.winehq.org/show_bug.cgi?id=17518 http://bugs.winehq.org/show_bug.cgi?id=19183
I submitted a patch to fix http://bugs.winehq.org/show_bug.cgi?id=17518 but it'd be nice to get some love on the others.
- Dan
Add: http://bugs.winehq.org/show_bug.cgi?id=19208 http://bugs.winehq.org/show_bug.cgi?id=19209
to the lists. I also get failures in comctl32/listview, but Nikolay thinks it's some other test not cleaning up well after itself (d3d perhaps?).
Austin English wrote:
On Sat, Jul 4, 2009 at 10:48 AM, Dan Kegeldank@kegel.com wrote:
We've had a test suite for six or so years now, and we keep getting closer to having it pass reliably, but we're still not quite there. I see from http://test.winehq.org that fifteen tests fail on at least one machine.
There are several bugs that only cause make test to fail if you run them with WINEDEBUG=warn+heap, but those seem just as important to me.
On my own machine, here are the bugs related to make test failures: http://bugs.winehq.org/show_bug.cgi?id=12925 http://bugs.winehq.org/show_bug.cgi?id=14078 http://bugs.winehq.org/show_bug.cgi?id=17414 http://bugs.winehq.org/show_bug.cgi?id=17518 http://bugs.winehq.org/show_bug.cgi?id=19183
I submitted a patch to fix http://bugs.winehq.org/show_bug.cgi?id=17518 but it'd be nice to get some love on the others.
- Dan
Add: http://bugs.winehq.org/show_bug.cgi?id=19208 http://bugs.winehq.org/show_bug.cgi?id=19209
to the lists. I also get failures in comctl32/listview, but Nikolay thinks it's some other test not cleaning up well after itself (d3d perhaps?).
But d3d comes after comctl32.
On Mon, Jul 6, 2009 at 1:15 AM, Paul Vrienspaul.vriens.wine@gmail.com wrote:
Austin English wrote:
On Sat, Jul 4, 2009 at 10:48 AM, Dan Kegeldank@kegel.com wrote:
We've had a test suite for six or so years now, and we keep getting closer to having it pass reliably, but we're still not quite there. I see from http://test.winehq.org that fifteen tests fail on at least one machine.
There are several bugs that only cause make test to fail if you run them with WINEDEBUG=warn+heap, but those seem just as important to me.
On my own machine, here are the bugs related to make test failures: http://bugs.winehq.org/show_bug.cgi?id=12925 http://bugs.winehq.org/show_bug.cgi?id=14078 http://bugs.winehq.org/show_bug.cgi?id=17414 http://bugs.winehq.org/show_bug.cgi?id=17518 http://bugs.winehq.org/show_bug.cgi?id=19183
I submitted a patch to fix http://bugs.winehq.org/show_bug.cgi?id=17518 but it'd be nice to get some love on the others.
- Dan
Add: http://bugs.winehq.org/show_bug.cgi?id=19208 http://bugs.winehq.org/show_bug.cgi?id=19209
to the lists. I also get failures in comctl32/listview, but Nikolay thinks it's some other test not cleaning up well after itself (d3d perhaps?).
But d3d comes after comctl32.
Sorry, should've been more clear. I don't typically reboot daily, so the previous day's d3d tests may be interfering with comctl32.
-
Austin English -
Dan Kegel -
Paul Vriens