[lldb-dev] Digging into Linux unexpected successes

Tamas Berghammer via lldb-dev lldb-dev at lists.llvm.org
Tue Sep 15 09:59:14 PDT 2015

Unfortunately the GCE logs aren't public at the moment and the amount of
them isn't make it easy to make them accessible in any way (~30MB/build)
and they aren't much more machine parsable then the stdout from the build.

I think downloading data with the json API won't help because it will only
list the failures displayed on the Web UI what don't contain full test
names and don't contain info about the UnexpectedSuccess-es. If you want to
download it from the web interface then I am pretty sure we have to parse
in the stdout of the test runner and change dotest in a way that it
displays more information about the outcome of the different tests.

On Tue, Sep 15, 2015 at 5:52 PM Todd Fiala <todd.fiala at gmail.com> wrote:

> Yep looks like there's a decent interface to it.  Thanks, Siva!
> I see there's some docs here too:
> http://docs.buildbot.net/current/index.html
> On Tue, Sep 15, 2015 at 9:42 AM, Siva Chandra <sivachandra at google.com>
> wrote:
>> On Tue, Sep 15, 2015 at 9:25 AM, Todd Fiala via lldb-dev <
>> lldb-dev at lists.llvm.org> wrote:
>>> > The cmake builder runs in GCE and it uploads all test logs to Google
>>> Cloud Storage (including full host logs and server logs). I used a python
>>> script (running also in GCE) to download this data and to parse the test
>>> output from the test traces.
>>> Are the GCE logs public?  If not, do you know if our buildbot protocol
>>> supports polling this info via another method straight from the build bot?
>> You are probably looking for this: http://lab.llvm.org:8011/json/help
> --
> -Todd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150915/591e1ab1/attachment.html>

More information about the lldb-dev mailing list