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.fi...@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 > > > >
_______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
