Bug 105873
| Summary: | bisect-builds should print instructions on how to continue bisecting with git | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | dbates, dpranke, inferno |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Eric Seidel (no email)
bisect-builds should print instructions on how to continue bisecting with git
In diagnosing bug 105861, I used bisect-builds for the first time in a long time:
bisect-builds -r 136278:136846 http://www.uofmchildrenshospital.org/Providers/Bio/D_122501
Works: r136298 Fails: r136812
....
Checking revision r136309 (0 builds left to test after this)...
Downloading WebKit-SVN-r136309.dmg to /Users/eseidel/Library/Caches/WebKit-Nightlies/trunk...
######################################################################## 100.0%
Mounting disk image and running WebKit...
Did the bug reproduce in r136309 (yes/no/broken)? yes
Works: r136298 Fails: r136309
http://trac.webkit.org/log/trunk/?rev=136309&stop_rev=136299
That's great, but not close enough, and it should tell me how to continue with git:
git bisect start [--no-checkout] [<bad> [<good>...]] [--] [<paths>...]
But it would need to lookup the git commits using:
git svn find-rev
(I just learned that Chromium has a bisect-builds.py: http://www.chromium.org/developers/bisect-builds-py I wonder if it explains how to move to WebKit when the offending revision is a webkit roll. :)
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Eric Seidel (no email)
bisect-builds is much much faster than git-bisect, but it can't get you all the way. Eventually you have to continue by hand, or continue with git. :)