Bug 103838 - Garden-o-matic shouldn't die when blank JSON results are received.
Summary: Garden-o-matic shouldn't die when blank JSON results are received.
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Mike West
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-02 12:24 PST by Mike West
Modified: 2012-12-02 13:19 PST (History)
4 users (show)

See Also:


Attachments
Patch (2.42 KB, patch)
2012-12-02 12:25 PST, Mike West
no flags Details | Formatted Diff | Diff
Patch for landing (2.43 KB, patch)
2012-12-02 13:03 PST, Mike West
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Mike West 2012-12-02 12:24:11 PST
Garden-o-matic shouldn't die when blank JSON results are received.
Comment 1 Mike West 2012-12-02 12:25:50 PST
Created attachment 177145 [details]
Patch
Comment 2 Ojan Vafai 2012-12-02 12:43:03 PST
Does this show an error in the UI? If not, we should at least show an error. This points to a bug on the buildbot side *and* it means we're not actually getting data for this bot.
Comment 3 Mike West 2012-12-02 12:47:39 PST
No. It throws an exception, and the UI sticks at "Loading commit data...".

Oh, sorry, you mean after this patch. I don't know, honestly. :) This is what would happen if the XHR request errored out (e.g. the error event is bound to 'callback({})', so if that visually errors off, this would too.
Comment 4 Ojan Vafai 2012-12-02 12:51:06 PST
(In reply to comment #3)
> Oh, sorry, you mean after this patch. I don't know, honestly. :) This is what would happen if the XHR request errored out (e.g. the error event is bound to 'callback({})', so if that visually errors off, this would too.

I see. I think we show an error in that case. Either way, this patch seems fine since we should fix it to show an error if the XHR fails if we don't already.
Comment 5 Mike West 2012-12-02 12:52:29 PST
Cool. Then I'll throw it into the queue (thanks for the r+, Adam. :) ).
Comment 6 WebKit Review Bot 2012-12-02 12:56:03 PST
Comment on attachment 177145 [details]
Patch

Rejecting attachment 177145 [details] from commit-queue.

Failed to run "['/mnt/git/webkit-commit-queue/Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '-..." exit_code: 2

Last 500 characters of output:
Kit/chromium/third_party/yasm/source/patched-yasm --revision 167605 --non-interactive --force --accept theirs-conflict --ignore-externals' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium'
52>At revision 167605.

________ running '/usr/bin/python tools/clang/scripts/update.py --mac-only' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium'

________ running '/usr/bin/python gyp_webkit' in '/mnt/git/webkit-commit-queue/Source/WebKit/chromium'
Updating webkit projects from gyp files...

Full output: http://queues.webkit.org/results/15104234
Comment 7 Mike West 2012-12-02 13:03:38 PST
Created attachment 177148 [details]
Patch for landing
Comment 8 WebKit Review Bot 2012-12-02 13:19:32 PST
Comment on attachment 177148 [details]
Patch for landing

Clearing flags on attachment: 177148

Committed r136352: <http://trac.webkit.org/changeset/136352>
Comment 9 WebKit Review Bot 2012-12-02 13:19:36 PST
All reviewed patches have been landed.  Closing bug.