RESOLVED FIXED37968
new-run-webkit-tests is unusable with crashing tests
https://bugs.webkit.org/show_bug.cgi?id=37968
Summary new-run-webkit-tests is unusable with crashing tests
Eric Seidel (no email)
Reported 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.
Attachments
Mark Rowe (bdash)
Comment 1 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.
Dirk Pranke
Comment 2 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?
Note You need to log in before you can comment on or make changes to this bug.