Bug 59256

Summary: only include failures in full_results.json
Product: WebKit Reporter: Ojan Vafai <ojan>
Component: New BugsAssignee: Ojan Vafai <ojan>
Status: RESOLVED FIXED    
Severity: Normal CC: abarth, dpranke, eric, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Attachments:
Description Flags
Patch tony: review+

Ojan Vafai
Reported 2011-04-22 16:38:16 PDT
only include failures in full_results.json
Attachments
Patch (3.92 KB, patch)
2011-04-22 16:39 PDT, Ojan Vafai
tony: review+
Ojan Vafai
Comment 1 2011-04-22 16:39:05 PDT
Ojan Vafai
Comment 2 2011-04-22 16:39:35 PDT
This patch depends on bug 59239.
Tony Chang
Comment 3 2011-04-22 19:17:24 PDT
Comment on attachment 90801 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=90801&action=review > Tools/Scripts/webkitpy/layout_tests/layout_package/manager.py:128 > + test_dict = {} It would be nice to just make these structs at some point. > Tools/Scripts/webkitpy/layout_tests/layout_package/manager.py:130 > + if False: > + test_dict['has_stderr'] = True Debugging code?
Dirk Pranke
Comment 4 2011-04-26 16:11:05 PDT
Comment on attachment 90801 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=90801&action=review > Tools/Scripts/webkitpy/layout_tests/layout_package/manager.py:74 > + """Summarize failing results as a dict. Unless I'm misunderstanding this, it looks like this change removes unexpected passes. That's bad - it'll break the bot output reporting unexpected passes and the log output for the same. It seems to me that if you want to exclude the results from the JSON file you should do it where you build the JSON file, not by changing this function.
Ojan Vafai
Comment 5 2011-04-27 11:20:56 PDT
(In reply to comment #4) > (From update of attachment 90801 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=90801&action=review > > > Tools/Scripts/webkitpy/layout_tests/layout_package/manager.py:74 > > + """Summarize failing results as a dict. > > Unless I'm misunderstanding this, it looks like this change removes unexpected passes. That's bad - it'll break the bot output reporting unexpected passes and the log output for the same. Good catch. Fixed. > It seems to me that if you want to exclude the results from the JSON file you should do it where you build the JSON file, not by changing this function. I don't see why. The only places the summarized results are used is to write out the json and print out unexpected failures. I don't really see that changing in the future, do you?
Ojan Vafai
Comment 6 2011-04-27 14:27:23 PDT
Dirk Pranke
Comment 7 2011-04-27 14:57:19 PDT
(In reply to comment #5) > (In reply to comment #4) > > (From update of attachment 90801 [details] [details]) > > View in context: https://bugs.webkit.org/attachment.cgi?id=90801&action=review > > > > > Tools/Scripts/webkitpy/layout_tests/layout_package/manager.py:74 > > > + """Summarize failing results as a dict. > > > > Unless I'm misunderstanding this, it looks like this change removes unexpected passes. That's bad - it'll break the bot output reporting unexpected passes and the log output for the same. > > Good catch. Fixed. > > > It seems to me that if you want to exclude the results from the JSON file you should do it where you build the JSON file, not by changing this function. > > I don't see why. The only places the summarized results are used is to write out the json and print out unexpected failures. I don't really see that changing in the future, do you? At some point I'd like to change the Manager.run() routine to return something like the summarized results so that we can write better integration tests, but it's a pretty low-priority thing.
Dirk Pranke
Comment 8 2011-04-27 14:58:35 PDT
Nit, since the summarized results kept the unexpected passes, the original docstring was more accurate. I think you forgot to change it back.
WebKit Review Bot
Comment 9 2011-04-27 15:39:04 PDT
http://trac.webkit.org/changeset/85095 might have broken Windows 7 Release (Tests)
Note You need to log in before you can comment on or make changes to this bug.