[Wine] Re: Performing a Regression Test
wineforum-user at winehq.org
Sat Oct 9 10:55:02 CDT 2010
> abb4 wrote:
> > Any help is appreciated!
> Ohh I see,
> have to go back to
> git bisect start
> git bisect good <wine-tag where program worked>
> git bisect bad <wine-tag where program stopped working>
> This is quite complicated stuff
Oke, got a bit further with this
The above was mistaken.
when I recompiled it didn't work with [./configure && make deps && make ] & I lost the wine branch
But with [CC="ccache gcc" ./configure --verbose && make depend && make] it compiled well
so I completely messed things up, so to say..
Now I got stuck somewhere else, please any help is apreciated!
This is how far I got, I found the bad commit, but to put this one at test, the following happened
> adri at dark:~/wine-git$ git bisect good
> 6d1ef3a6a64f0fabf05ce1bba5f0ec4373684786 is the first bad commit
> commit 6d1ef3a6a64f0fabf05ce1bba5f0ec4373684786
> Author: Huw Davies <huw at codeweavers.com>
> Date: Thu Jul 22 13:37:19 2010 +0100
> ole32: Implement cross-process drag and drop.
> :040000 040000 ab88cc6bf0936bc4adc7bff0673415282613d919 065c727204a46
> make clean
> adri at dark:~/wine-git$ git reset --hard
> HEAD is now at a2e1dd2 ole32/tests: Relax the reference counting tests a bit. We only care whether references are held or not.
> adri at dark:~/wine-git$ git show 6d1ef3a6a64f0fabf05ce1bba5f0ec4373684786 | patch -p1 -R
> patching file dlls/ole32/ole2.c
> Unreversed patch detected! Ignore -R? [n] enter
> Apply anyway? [n] y
> Hunk #1 FAILED at 116.
> Hunk #2 FAILED at 270.
> Hunk #3 FAILED at 406.
> Hunk #4 FAILED at 436.
> Hunk #5 FAILED at 477.
> Hunk #6 FAILED at 491.
> Hunk #7 FAILED at 2143.
> Hunk #8 FAILED at 2171.
> Hunk #9 FAILED at 2183.
> 9 out of 9 hunks FAILED -- saving rejects to file dlls/ole32/ole2.c.rej
What should been done with a 'Unreversed patch detected!'
Or can I be sure the detected bad commit is the right one?
How to proceed?
More information about the wine-users