[Wine] Re: Performing a Regression Test

zac wineforum-user at winehq.org
Sun Mar 7 07:37:13 CST 2010


Hello folks!
I'm back!

Regression testing is a lot of work!
I still don't know if I did everything right, though. Again, I think I need help.

I'm posting here all the results of the bisecting process. When I got the 'Bisecting: 0 revisions left to test after this' I don't seem to have received the 'bad commit' I was expecting!


Code:

debian:/home/zac/wine-git# git bisect good
Bisecting: 1211 revisions left to test after this
[853d993830509c3ecaa4113bed789bf08ec36d76] shell32: Default to the more modern location for the user profile directory.

--------------------------
debian:/home/zac/wine-git# git bisect bad
Bisecting: 605 revisions left to test after this
[7aa3bb3a68b1b1d5b01ace0dd9fc896c59375e99] sane.ds: Initialize the SupportedGroups field when returning a source.

-------------------------------
debian:/home/zac/wine-git# git bisect good
Bisecting: 302 revisions left to test after this
[edef19f8d60d6ce089f1562a958925668f9d4e32] d3dx8: Move some functions into core.c to match the header file layout.

--------------------------------
debian:/home/zac/wine-git# git bisect bad
Bisecting: 151 revisions left to test after this
[5bc54ed97ecd281a2ef4d07473d72f1e50cd9ad5] gdiplus: Implemented GdipCreateBitmapFromHICON (with tests).

----------------------------------
debian:/home/zac/wine-git# git bisect bad
Bisecting: 75 revisions left to test after this
[dd943665932e428c3f423ae062464d9b4d755ea5] wininet/tests: Fix tests failures on W2K and below and some early XP.

--------------------------------------
debian:/home/zac/wine-git# git bisect good
Bisecting: 37 revisions left to test after this
[f20ba244049f5473369e32df5fe108244da3e180] d3dx8: Implement D3DXFresnelTerm.

---------------------------
debian:/home/zac/wine-git# git bisect good
Bisecting: 18 revisions left to test after this
[183bb795b6c1cd1e24503a20b1a4a7b9ec12524b] mshtml: Add missing StyleSheet interfaces.

-----------------------------------
debian:/home/zac/wine-git# git bisect bad
Bisecting: 9 revisions left to test after this
[e7d58bdd5243d31dec0f7c735566b6b9744ddf7b] itss: Move buffer initialization a bit up (Coverity).

--------------------------------
debian:/home/zac/wine-git# git bisect bad
Bisecting: 4 revisions left to test after this
[edbea606f94a34872097620e2b79e9c07fa3c921] comctl32: Fix propsheet size calculation.

---------------------------------
debian:/home/zac/wine-git# git bisect bad
Bisecting: 1 revisions left to test after this
[8662c6fe7b60d9ff563ba790d4431ef30250249b] richedit: Implement EM_GETTEXTMODE.

------------------------------------
debian:/home/zac/wine-git# git bisect bad
Bisecting: 0 revisions left to test after this
[1a3551b630eae2418692f21790fcc7fc973f5366] richedit: Use width from EM_SETTARGETDEVICE for wrapping.




Sorry guys... What should I do now? I was expecting to get the bad commit and its author, so that I could post that into bugzilla... But since I didn't, I don't know how to proceed.

Should I do something like the following?


Code:

make clean
git reset --hard
git show <commit number, usually a 32 alphanumeric> | patch -p1 -R





Thank you very much for your help!







More information about the wine-users mailing list