"auto_explore" past the first and last commits

catapult-project / catapult

Deprecated Catapult GitHub. Please instead use http://crbug.com "Speed>Benchmarks" component for bugs and https://chromium.googlesource.com/catapult for downloading and editing source code..

https://chromium.googlesource.com/catapult

BSD 3-Clause "New" or "Revised" License

1.93k stars 563 forks source link

"auto_explore" past the first and last commits #3928

Open dave-2 opened 6 years ago

dave-2 commented 6 years ago

Sometimes we don't know the correct start and end points for a bisect.

An alert is in the wrong place, and we don't know what the right place is.
A flaky test started failing, and we don't know exactly when it started.

As part of the "auto_explore" logic, we could potentially expand the bisection range beyond the given commits.

@perezju @simonhatch @anniesullie @nedn

dave-2 commented 6 years ago

The biggest open question I have for this feature is how to know far back and forward to look. Some multiple of the original revision range? Up to a fixed number of revisions? If we make the range too large, we could end up with a lot of extraneous positive results.

Another question is whether we can look forward using the Gitiles API.