[LLVMdev] LIT Verbose

David Blaikie dblaikie at gmail.com
Mon Dec 22 15:46:09 PST 2014

On Sat, Dec 20, 2014 at 2:00 AM, Renato Golin <renato.golin at linaro.org>
> On 19 December 2014 at 17:29, Daniel Sanders <Daniel.Sanders at imgtec.com>
> wrote:
> > My understanding was the other way around. The tests timeout but they
> shouldn't. However, re-reading the original email I see that my mind
> inserted a word that isn't there.
> > Renato, just to double check: Is it failing _due_ to timeout? Or failing
> to timeout?
> Each test runs correctly and successfully, but all together take
> longer to run than the overall timeout.
> Unlike the make version, ninja doesn't print each test as they run,
> but after they have all finished, so you only have one output for
> several minutes "Running tests".

A recent change (to lit? to cmake? to ninja?) causes this not to be the
case, at least on interactive builds. I actually now get the lit progress
bar UI & everything.

Piping that output to a file... I get this:

Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90..

So maybe that's working too? (though it's not printing out every file, it's

> The buildmaster kills the slave after a long time without receiving
> input, but that doesn't mean the slave is locked. It just means that
> the slave is not sending progress updates as it works through the
> tests.
> What I'm trying to enable is ninja to print each test as they run, not
> all at the end.
> Though, I'll be out until January without my laptop, so that'll be
> after the holidays. :)
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20141222/c3c66293/attachment.html>

More information about the llvm-dev mailing list