wine users - May 2011 - [Regression Testing]Questions

Hi,

I do a regression testing actually for "AC : Brotherhood" because this
game crash with wine 1.3.19 and not for old version.

I read the wiki for the regression testing and i have questions for the test.
To begin the test, i launch these command :

Code:
git bisect start
git bisect good wine-1.3.18
git bisect bad wine-1.3.19



For exemple, i have 

Code:
Bisecting: 150 revisions left to test after this



After to compile wine and run the game, it crash always. Result, the bug is
still present so i launch :

Code:
git bisect bad
Bisecting: 75 revisions left to test after this



I recompile wine and when i test the game, it doesn't crash so i launch :

Code:
git bisect good
Bisecting: 36 revisions left to test after this



My question is :
if the bug is present or not, i must to launch "git bisect bad/good"
to see :

Code:
Bisecting: 0 revisions left to test after this

Berillions wrote:
> Bisecting: 0 revisions left to test after this
You have one last compile, test, git bisect good/bad left.

On 5/8/11 4:08 AM, Berillions wrote:
> Hi,
>
> I do a regression testing actually for "AC : Brotherhood" because
this game crash with wine 1.3.19 and not for old version.
>
> I read the wiki for the regression testing and i have questions for the
test.
> To begin the test, i launch these command :
>
> Code:
> git bisect start
> git bisect good wine-1.3.18
> git bisect bad wine-1.3.19
>
>
>
> For exemple, i have
>
> Code:
> Bisecting: 150 revisions left to test after this
>
>
>
> After to compile wine and run the game, it crash always. Result, the bug is
still present so i launch :
>
> Code:
> git bisect bad
> Bisecting: 75 revisions left to test after this
>
>
>
> I recompile wine and when i test the game, it doesn't crash so i launch
:
>
> Code:
> git bisect good
> Bisecting: 36 revisions left to test after this
>
>
>
> My question is :
> if the bug is present or not, i must to launch "git bisect
bad/good" to see :
>
> Code:
> Bisecting: 0 revisions left to test after this
>
Keep going as you have to see a 'first bad commit' is:  line.

One more time should be enough.

Don't forget to file a bug report if the removing the bad commit causes 
the program to run.

James McKenzie

Hey james, you have the rule now that you ignoring all other posts since you
became an admin? You do not need to ask the same question twice.