search for: _due_

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? > -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On > Behalf Of Jonathan Roelofs > Sent: 18 December 2014 22:09 > To: Renato Golin > Cc: LLVM Dev > Subject: Re: [LLVMdev] LIT Verbose...

...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 o...

On 18 December 2014 at 21:32, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > I think this will help one facet of your problem: > http://reviews.llvm.org/D6584 I don't think so, because the tests don't time out, it's a buffering issue... --renato

...imgtec.com<mailto: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 &qu...