| Summary: | run-webkit-tests -2 does not show stacktraces for crashes on Qt | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | WebKit Review Bot <webkit.review.bot> |
| Component: | New Bugs | Assignee: | WebKit Review Bot <webkit.review.bot> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | aroben, benjamin, dpranke, eric, kbalazs, kling, menard, ossy |
| Priority: | P2 | Keywords: | NRWT, Qt, QtTriaged |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 56729 | ||
| Bug Blocks: | 64491 | ||
|
Description
WebKit Review Bot
2011-08-25 11:45:36 PDT
In NRWT crashlog discovery can be found here: http://trac.webkit.org/browser/trunk/Tools/Scripts/webkitpy/common/system/crashlogs.py For ports which spit out the crash log to stderr the crash handling is inside the driver, I think. Note that run-webkit-tests -2 uses ORWT at the moment. But if we're going to add this feature, we might as well add it to NRWT. ORWT is soon to be dead. :) Is this still an issue? run-webkit-tests -2 switched to using new-run-webkit-tests tonight. If Qt is dumping the crash log to stderr, we'll display it. :) I don't know ... But Qt uses NRWT for WK2 testing long time ago. I'm sure it's not an NRWT issue bug a problem with Qt specific the crash logging code in WTR. One know limitation is that it's only works for crashes in the web process. I will take a look how could it be improved. I tried it locally with a random crash in the web process and the crash logs were ok. Could you point to a particular build at the bot where crash log was missing? It isn't problem now, we get crash logs regularly. There are missing crash logs sometimes, but they can't be reproducible and I don't think if they are NRWT related. |