[Bug 7915] 15 of the internal tests of wine fail on Mac OS X

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=7915


Austin English <austinenglish at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |austinenglish at gmail.com




--- Comment #21 from Austin English <austinenglish at gmail.com>  2008-10-26 21:11:08 ---
(In reply to comment #19)
> > Also, please file individual bugs, metabugs are discouraged in Wine bugzilla.
> 
> sorry i don't have time for this ATM.
> also
> • the linux version of this bug (bug 9916) is a metabug too

That's why it's so hard to track progress on that bug. Initially, it made a lot
of progress, now it's a mess.

> • just because i file 47 bugs now nobody will suddenly start working on this

True, but they're much harder to fix without proper information (debug traces,
etc.)

> > Also, be sure to file a bug report with Apple, so that they can do their part to fix it on their end.
> 
> filing bugs with apple is useless unless you are an paying developer in
> addition to being an paying customer. also i'm not sure what issues you are
> referring to, the X11 crash didn't occur this time, 10.5.5 helped a lot in X11
> land.

That X11 crash was reported to Apple a lot before it was fixed. While most of
the issues may be Wine bugs, it can't hurt to have Apple looking at it from
their end. 

(In reply to comment #20)
> Indeed.  There's really no need to file bugs for failing test
> cases... the thing to do is to make sure our existing
> (semi-)automated test systems (http://test.winehq.org, patchwatcher)
> are reporting data for the Mac.

I have to disagree Dan. A lot of these are probably dupes of the Solaris or
FreeBSD bugs already filed. Only submitting data on test.winehq.org may get
overlooked, while bugs are much more noticeable. While they may not get looked
at for a while, these tests are much easier to fix if individually filed as
bugs, with appropriate traces and other reporting information.

> (As far as patchwatcher goes, we're working on
> making this easier... it's a work in progress.)
> 

+1, using patchwatcher to prevent NEW bugs from getting in would be excellent.


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.