Bug 58481 - Impossible to tell from results.json/results.html if run was complete or not
Summary: Impossible to tell from results.json/results.html if run was complete or not
Status: RESOLVED FIXED
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: 2011-04-13 14:32 PDT by Eric Seidel (no email)
Modified: 2012-07-17 11:34 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 2011-04-13 14:32:00 PDT 
Impossible to tell from results.json/results.html if run was complete or not

I'm having to write a whole bunch of code in the commit-queue to guess if a run was complete or not.  results.json and results.html should record this information.  Specifically what the --exit-after-N-failures value was, or just if the result completed.

I want to be able to tell if a test failed or passed definitively from a results archive.  Currently that's impossible without apriori knowledge about how the tests were run.
Comment 1 Dirk Pranke 2011-04-13 14:33:22 PDT 
Seems like this would be a good enhancement.
Comment 2 Ojan Vafai 2012-07-17 11:34:04 PDT 
full_results.json now has an interrupted key.