Project

General

Profile

Actions

Task #1263

closed

Change bibisect behavior to prevent wasted time

Added by Joel Madero over 9 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
Normal
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Tags:

Description

I'm not entirely sure how bibisect works but I don't think it's as efficient as it could be.

The best bet would be that the first test is always the oldest commit, and the second commit always be the latest commit in the package.

The only time a third (and continuing) test would be needed is if the bug is not present in the first (oldest) and is present in the second (lastest).

Currently the issue is that you have to do an entire bibisect (8-12 checks) even if the bug isn't present ever in the bibisect package or is inherited from OOo.

What should happen:

1. Present in the oldest pull (first test) - bibisect should spit put "this bug is inherited from OOo"
2. Not present in oldest pull but present in second (newest) - full test required to bibisect
3. Not present in 1st or 2nd pull - no need to continue, bibisect should state "this bug was introduced during the commit range of this bibisect package"

If we hope to continue moving towards more bibisecting - ideally bibisecting every single bug - this will save a ton of time.

Thanks

Actions

Also available in: Atom PDF