Bug 30136 - run-webkit-tests should link to crash reports from results.html
Summary: run-webkit-tests should link to crash reports from results.html
Status: RESOLVED DUPLICATE of bug 14861
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: 2009-10-06 12:50 PDT by Eric Seidel (no email)
Modified: 2009-10-28 09:45 PDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2009-10-06 12:50:06 PDT
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.
Comment 1 Mark Rowe (bdash) 2009-10-06 13:02:18 PDT
It’s worth noting that the locations and file names for crash logs are not the same on Tiger, Leopard and SnowLeopard.
Comment 2 Eric Seidel (no email) 2009-10-06 13:15:48 PDT
Hum... good to know.  I guess I'll write the Leopard implementation and we can later make the magic work on other operating systems. :)
Comment 3 Eric Seidel (no email) 2009-10-06 13:54:47 PDT
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).
Comment 4 Eric Seidel (no email) 2009-10-28 09:45:30 PDT

*** This bug has been marked as a duplicate of bug 14861 ***