[Bug 2931] Diablo 2 video test fails

[Wine Bugs]

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





------- Additional Comments From Speeddymon at gmail.com  2005-07-05 10:51 -------
ok, apparently I am going blind, as I just typed exatcly what you asked..  Sorry
about that!  Scratches head...

Basically you have completed the easy part of the work of running a regression
test, in that you determined the last known working date, and first known
non-working date.  But the hard part is finding the right time (which can be a
little tedious).  If you find the right time (down to the second as the
instructions say), then we eliminate all other patches committed during that day
as being a problematic patch.

A lot of times running a regression test will reveal that a patch that has
nothing to do with the bug in question (a soung patch breaking something video
related in a game) is somehow the culprit.. By fixing a bug in one part of wine
(or adding a new one as is what sometimes happens), we reveal a bug in another part.

Now of course most of the time that is not the case, we end up with a patch
being revealed as problematic that directly affects video related stuff, and so
it is much easier (not to mention quicker) to fix than the case above..

That is why we have the specific instructions for running the regression test,
to determine exactly which patch caused it, so we know who to forward the bug
to, whether it is the person that contributed a video fix that broke the video
test of D2, or the one that contributed a sound fix that somehow broke the video
test of D2.

Hope all of that clears things up for you a bit

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.