[Lldb-commits] [PATCH] D12831: Add JUnit/XUnit-formatted output to the lldb test run system

Zachary Turner via lldb-commits lldb-commits at lists.llvm.org
Sat Sep 12 17:21:36 PDT 2015

I can't check this until Monday.  But drive by comment: Why do we need the
MAPMODE?  Can't the JUnitFormatter just treat xpasses as whatever it wants
without the help of this option?

Also, I'm not really familiar with JUnit as a general tool.  Is there some
reason a one-size-fits-all JSON formatter is insufficient?

Last question: Is the current stdout/stderr formatter re-written as a
second formatter plugin, or not?

On Sat, Sep 12, 2015 at 3:26 PM Todd Fiala <todd.fiala at gmail.com> wrote:

> tfiala added a comment.
> A couple notes on this:
> - Failures don't currently capture backtraces.  I can add this later, but
> I am leaving it for another pass.  This change is big enough as is.  Right
> now I'm focusing on counts and green/red CI solutions.
> - Tests don't capture testcase-specific stdout/stderr.  This is too big a
> change for right now.  We can get there but not until we stop depending on
> the stdout/stderr going to other places for the whole test run.
> Skip reason is captured, as are bug numbers, exception types and exception
> messages, stuffed into relevant JUnit xml attributes.
> http://reviews.llvm.org/D12831
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150913/d64d0027/attachment.html>

More information about the lldb-commits mailing list