Bug 37968 - new-run-webkit-tests is unusable with crashing tests
Summary: new-run-webkit-tests is unusable with crashing tests
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-21 21:25 PDT by Eric Seidel (no email)
Modified: 2011-08-08 10:11 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 Eric Seidel (no email) 2010-04-21 21:25:12 PDT 
new-run-webkit-tests is unusable with crashing tests

ReportCrash is killing us.

NRWT can easily end up getting one ReportCrash running for each of your cores.  Once that happens your machine is basically locked and unusable (not to mention all the tests timing out).

We need to either disable ReportCrash, or find some way to pause all tests to wait for it to be done.
Comment 1 Mark Rowe (bdash) 2010-04-21 23:49:47 PDT 
One thing I’ve heard is that using dSYMs results in ReportCrash being significantly faster since all of the debug information is in a single contiguous file rather than being scattered over thousands of object files.  Can you see whether enabling the use of dSYMs improves things at all?  That’d be the best solution if it does address the issue.
Comment 2 Dirk Pranke 2010-04-22 18:58:38 PDT 
how is this different than ORWT? The fact that we're running stuff in parallel can massively increase the load on your machine rather than just pinning one thread and ORWT itself?