Bug 16903 - Add a "bisect-tests" tool to find tests that leak
Summary: Add a "bisect-tests" tool to find tests that leak
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac OS X 10.5
: P3 Enhancement
Assignee: Nobody
URL:
Keywords: InRadar, ToolsHitList
Depends on:
Blocks:
 
Reported: 2008-01-16 23:38 PST by mitz
Modified: 2011-11-05 18:19 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mitz 2008-01-16 23:38:12 PST 
When tracking down a memory leak seen on build bot, I try to narrow it down to one layout test that causes the leak, by repeatedly invoking run-webkit-tests --leaks with smaller sets of tests. However, there is no easy way to specify a continuous range of tests, and there is no way to automate the process.

Building "range" support into run-webkit-tests and adding "bisect" functionality either in run-webkit-tests or in a wrapper script will help speed up the process.
Comment 1 David Kilzer (:ddkilzer) 2008-01-17 02:07:15 PST 
Definitely similar to Bug 16873.  Would be nice to be able to define what "failure" is in this case (whether it's a leak or a failing test).
Comment 2 Adam Roben (:aroben) 2011-05-26 11:44:21 PDT 
<rdar://problem/9509302>