[Wine] Performing a Regression Test

James McKenzie jjmckenzie51 at earthlink.net
Sun Mar 7 13:15:06 CST 2010

mogorva wrote:
> Well, I'm very inexperienced in regression testing too, and have a question:
> I filed a bugreport about a possible regression that prevents Alpha Prime from runnning correctly:  
> http://bugs.winehq.org/show_bug.cgi?id=21941
> I tried to revert the patch that might caused the problem in the game following this guide: http://wiki.winehq.org/RegressionTesting
> So I made the following in the wine-git directory:
> git bisect reset
> then
> git show 224043d6cf8b56e9ff2537358646700211d54d1f | patch -p1 -R
> but the result was this:
> patching file dlls/wined3d/buffer.c
> Hunk #3 FAILED at 1058.
> Hunk #4 succeeded at 1098 (offset 3 lines).
> Hunk #5 succeeded at 1105 (offset 3 lines).
> Hunk #6 succeeded at 1148 (offset 3 lines).
> Hunk #7 succeeded at 1156 (offset 3 lines).
> Hunk #8 succeeded at 1251 (offset 3 lines).
> 1 out of 8 hunks FAILED -- saving rejects to file dlls/wined3d/buffer.c.rej
> What should I do now?
It appears that a further patch has changed the contents of the file
from when the patch was originally published. 

So, more work has to be done.  You could use git blame to find out the
latest patch and then revert that patch and then revert the patch that
causes problems and then apply the follow-on patch, or you can revert
the patches, build Wine without them and see if the problem is gone.

I recommend the latter and then working through the new patches,
one-by-one to see if any of the follow-on patches cause problems as well.

James McKenzie

More information about the wine-users mailing list