Bug 30136
| Summary: | run-webkit-tests should link to crash reports from results.html | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | mrowe |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Eric Seidel (no email)
run-webkit-tests should link to crash reports from results.html
We'd also need to copy them to the results directory for upload when the bots are running the tests.
Crash reports are dumped to ~/Library/Logs/CrashReporter
They're formated like this:
DumpRenderTree_2009-01-16-160105_SilverTop.crash
DumpRenderTree_2009-02-03-105256_SilverTop.crash
DumpRenderTree_2009-02-03-110925_SilverTop.crash
So we would need to just get a directory listing, and figure out which ones occurred since when the tests started. We can even do the wiring up right after we notice the test crashed, and just take the most recent DumpRenderTree_*.log.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Mark Rowe (bdash)
It’s worth noting that the locations and file names for crash logs are not the same on Tiger, Leopard and SnowLeopard.
Eric Seidel (no email)
Hum... good to know. I guess I'll write the Leopard implementation and we can later make the magic work on other operating systems. :)
Eric Seidel (no email)
I look at this briefly. On the mac, we don't actually wait for the process to fully crash. So we'd have to make a guess at the end of the run-webkit-tests run as to which logs correspond to which crashes (assuming the DRT instances are done crashing at that point).
Eric Seidel (no email)
*** This bug has been marked as a duplicate of bug 14861 ***