[Lldb-commits] [Diffusion] rL238467: Refactor test runner to print sub-test-case pass/fail rate.

[Zachary Turner]

So when the issue was first discovered (or posted about) back in June, it
was unfortunately on my last day in the office before leaving for 5 weeks
and I couldn't get to it before leaving.  I'm back, but now that a bit of
time has passed, I'm having a hard time figuring out what the best thing to
do here is.

I'm quite confident that the drop in tests is simply a reporting issue, but
it's hard to be more concrete than this without having a before and after
comparison of the exact tests that were run before my patch, and the exact
tests that were run after my patch.

If I had to hazard a guess, I'd say the difference comes from skipped tests
being added to the lldb_total result now, but not before.

On Tue, Jul 14, 2015 at 2:46 PM Adrian McCarthy <amccarth at google.com> wrote:

> amccarth added a comment.
>
> Can you give an example of a specific test that's no longer running?  I'm
> trying to figure out if there are actually tests being skipped or if it's
> just a reporting problem.  On Windows, we're reporting a slightly higher
> number (369) than the sum of the "Ran n tests" lines (342).
>
>
> Users:
>   zturner (Author)
>   dawn (Auditor)
>
> http://reviews.llvm.org/rL238467
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150720/22a4041b/attachment.html>