[lldb-dev] Digging into Linux unexpected successes

[Todd Fiala via lldb-dev]

Change http://reviews.llvm.org/D12831 in review (waiting on Windows results
for that) adds a test event stream that supports pluggable test event
formatters.  The first formatter I've added is JUnit/XUnit output.  That's
to support typical JUnit/XUnit output handling built into most commercial
and open source CI solutions.  But that eventing mechanism is intended to
support quite a wider range of possible applications, including outputting
to different formats, displaying test results as they occur in different
viewers/controllers, etc.

-Todd

On Tue, Sep 15, 2015 at 10:33 AM, Siva Chandra <sivachandra at google.com>
wrote:

> On Tue, Sep 15, 2015 at 9:59 AM, Tamas Berghammer <tberghammer at google.com>
> wrote:
>
>> 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.
>>
>
> I fully support making those changes to dotest. Also, it would be nice to
> actually have a stats cron running along with the master with a webui,
> something like this: https://build.chromium.org/p/chromium/stats and
> http://build.chromium.org/f/chromium/flakiness/. Its a tall ask, but at
> the very least, we should have dotest.py put out machine readable output.
> This could be done on request (as in, when a certain flag is set).
>



-- 
-Todd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150915/40714c6f/attachment.html>