RESOLVED FIXED 36768
sheriff-bot fails to get information about certain builds 
https://bugs.webkit.org/show_bug.cgi?id=36768
Summary sheriff-bot fails to get information about certain builds
Adam Barth
Reported 2010-03-29 11:48:20 PDT
Error fetching data for Windows Debug (Build) build 12867 (http://build.webkit.org/bui lders/Windows%20Debug%20%28Build%29/builds/12867)
Attachments
Patch (1.92 KB, patch)
2010-03-29 18:05 PDT, Eric Seidel (no email) 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1 2010-03-29 13:12:27 PDT
To be clear, the sheriff bot doesn't actually parse the pages, but rather uses xmlrpc. I expect the buildbot is sometimes just fussy and decides not to reply, but we'll have to test that theory. http://trac.webkit.org/browser/trunk/WebKitTools/Scripts/webkitpy/common/net/buildbot.py#L308 is the xmlrpc code.
Adam Barth
Comment 2 2010-03-29 13:19:09 PDT
Error fetching data for Chromium Linux Release build 3915 (http://build.webkit.org/builders/Chromium%20Linux%20Release/builds/3915)
Adam Barth
Comment 3 2010-03-29 17:47:47 PDT
Error fetching data for Chromium Win Release build 4027 (http://build.webkit.org/builders/Chromium%20Win%20Release/builds/4027)
Eric Seidel (no email)
Comment 4 2010-03-29 17:58:38 PDT
This appears to be: http://buildbot.net/trac/ticket/753 Error fetching data for Chromium Win Release build 4028 (http://build.webkit.org/builders/Chromium%20Win%20Release/builds/4028): <Fault 8002: "Can't serialize output: cannot marshal None unless allow_none is enabled"> I've tried setting allow_none when creating the ServerProxy but that doesn't change anything.
Eric Seidel (no email)
Comment 5 2010-03-29 18:05:12 PDT
Created attachment 51989 [details] Patch
Adam Barth
Comment 6 2010-03-29 18:05:44 PDT
Comment on attachment 51989 [details] Patch As if this will do anything. :)
Eric Seidel (no email)
Comment 7 2010-03-29 18:08:20 PDT
Committed r56754: <http://trac.webkit.org/changeset/56754>
Note You need to log in before you can comment on or make changes to this bug.