Bug 37968
| Summary: | new-run-webkit-tests is unusable with crashing tests | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | abarth, dpranke, ojan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Eric Seidel (no email)
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 | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Rowe (bdash)
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
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?
Eric Seidel (no email)
I think we can consider this solved by Adam's work:
http://trac.webkit.org/changeset/90277
http://trac.webkit.org/changeset/90246
http://trac.webkit.org/changeset/89899
http://trac.webkit.org/changeset/89881