wine users - Jan 2009 - Regression test - bad rev input

Hi,
I have been trying to do a regression test between 1.1.10 and 1.1.12, as there
seems to be a number of problems with the installation of the Macromedia suite
(Dreamweaver, Fireworks, Flash).
I think I have ccache installed.
I think I have git OK.
I run git bisect start ok,
Then when I run git bisect good wine 1.1.10, I get:
Bad rev input: wine 1.1.10.

What am I doing wrong?

I have found the problem,
I mistyped the line.
Should have been 
git bisect good wine-1.1.10
(Missed the -hyphen)

Austin, Thanks. 
I have done 

Code:
 sudo apt-get install git-core


and it said:

Code:
Reading package lists... Done
Building dependency tree       
Reading state information... Done
git-core is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



Also, it shows I already have version 1.5.4.3
Now when I run:

Code:
git clone git://source.winehq.org/git/wine.git wine-git


I get:

Code:
'wine-git' already exists.

Thanks Vitamin.
I have now done the 

Code:
cd wine-git
git pull


Seemed to work except for the last line which said:

Code:
fatal: Entry '.gitignore' not uptodate. Cannot merge.


So which step of regression testing should I be up to now?

Code:
$ git bisect reset
$ git reset --hard origin
$ git fetch
$ git rebase origin


Now done that Austin - thanks,
Now I seem to be on my way...

> 8c4a2978b281e9519a6581d859add636de4b42d4 is the patch fixing this. 
Am I supposed to do anything with this piece of information?

I've done the git bisect skip. Doing the visualize step required an
installation, but it is well worth it, as the visualisation makes me feel more
comfortable seeing what is going on. :D
The one that I 've now done the skip on is:
947976f22cb80a0cb14cc3da71622a62f9628968

I have re-started with one on the good side, (b15ba). I think I am on my way
again.

Thanks Austin, I eventually worked out the significance of what you posted. 
With the great pointers of using gitk, I used it to help me narrow it down. I
have been able to say that the regression for installing Dreamweaver et al
occurred between:
Bisect good:
3c114a88ca1752ac07fe039d0471f89384ea4704
and Bisect bad:
8c4a2978b281e9519a6581d859add636de4b42d4

As I cannot work out what to do between these, I feel I am stuck as I cannot
test what I cannot compile. I can only post this information in the Bugzilla,
though I am not sure how it will be useful, with 23 revisions yet to test.

On Fri, Jan 9, 2009 at 7:19 PM, Col <wineforum-user at winehq.org>
wrote:
> Thanks Austin, I eventually worked out the significance of what you posted.
> With the great pointers of using gitk, I used it to help me narrow it down.
I have been able to say that the regression for installing Dreamweaver et al
occurred between:
> Bisect good:
> 3c114a88ca1752ac07fe039d0471f89384ea4704
> and Bisect bad:
> 8c4a2978b281e9519a6581d859add636de4b42d4
>
> As I cannot work out what to do between these, I feel I am stuck as I
cannot test what I cannot compile. I can only post this information in the
Bugzilla, though I am not sure how it will be useful, with 23 revisions yet to
test.
>
>
>
>
>
>
Have you tried in current git? I may have missed you saying that...

-- 
-Austin

Dear Austin,

I started with wine 1.1.12 as bad.
What do you mean by current git?

On Fri, Jan 9, 2009 at 7:33 PM, Col <wineforum-user at winehq.org>
wrote:
> Dear Austin,
>
> I started with wine 1.1.12 as bad.
> What do you mean by current git?
>
>
>
>
>
>
$ git reset --hard origin
$ git fetch ; git rebase origin
$ ./configure && make depend && make

That will give you the current development version. Try that. 1.1.12
had a couple major regressions.

-- 
-Austin

Thanks Austin, 

I have now also tested on the current git.
Installation fails on the current git. (Current git is bad).

My son worked out from gitk what was involved in doing a bisect by taking the
fix in 8c4a2978b281e9519a6581d859add636de4b42d4 and applying it where the bisect
would have been done. This was done by manually editing the configure and
configure.ac with the changes in the fix (after backing up from the changes),
and compiling. (We reversed our manual changes after testing).

For example this showed that 1a71479fbde0c10ad946334c524c3fdcb7dfab01 is good.

Is there any problem with continuing with this method?

On Fri, Jan 9, 2009 at 9:32 PM, Col <wineforum-user at winehq.org>
wrote:
> Thanks Austin,
>
> I have now also tested on the current git.
> Installation fails on the current git. (Current git is bad).
>
> My son worked out from gitk what was involved in doing a bisect by taking
the fix in 8c4a2978b281e9519a6581d859add636de4b42d4 and applying it where the
bisect would have been done. This was done by manually editing the configure and
configure.ac with the changes in the fix (after backing up from the changes),
and compiling. (We reversed our manual changes after testing).
>
> For example this showed that 1a71479fbde0c10ad946334c524c3fdcb7dfab01 is
good.
>
> Is there any problem with continuing with this method?
>
>
>
>
>
>
No, that should work fine. See http://wiki.winehq.org/ReverseRegressionTesting

-- 
-Austin