similar to: [LLVMdev] LIT Verbose

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

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

Hi, > Cool, I hope this succeeds. I tried implementing per-test timeouts before, and couldn't get it to work in all cases. The review eventually fizzled out, and I abandoned it. > > Here's that old review: http://reviews.llvm.org/D6584 Perhaps you can cannibalize testcases from it. Thanks for that. I'll take a look. > >> >> I'm e-mailing llvm-dev rather

Hi, A feature I've wanted in lit for a while is a having a timeout per test. Attached are patches that implement this idea. I'm e-mailing llvm-dev rather than llvm-commits because I want to gather more feedback on my initial implementation and hopefully some answers to some unresolved issues with my implementation. Currently in lit you can set a global timeout for all of the tests but

Try: make check-all LIT_ARGS="-s -j10" To limit the threads to 10, for example. On Wed, Jan 16, 2013 at 1:38 PM, Redmond, Paul <paul.redmond at intel.com> wrote: > Hi, > > Does anyone know how I can set the number of threads lit uses when invoked by make check? Lit has the —threads argument but this doesn't get set when run through make so it uses the max number of

I've looked at it a bit more and an updated ninja is part of it. You also need build.ninja to contain 'pool = console' on the lit rules. I added it manually to try it out but presumably a cmake update is needed to add this automatically. ________________________________ From: Renato Golin [renato.golin at linaro.org] Sent: 23 December 2014 00:55 To: David Blaikie Cc: LLVM Dev; Daniel

On Sat, Dec 20, 2014 at 2:00 AM, Renato Golin <renato.golin at linaro.org> wrote: > > 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. >

Hi, Does anyone know how I can set the number of threads lit uses when invoked by make check? Lit has the —threads argument but this doesn't get set when run through make so it uses the max number of cpus. paul

I'm just wondering if anyone's using Ninja (which buffers output from subcommands, such as lit/FileCheck/etc) & has thought about/found a way to force FileCheck to use colour in spite of Ninja's buffering. Thanks, - David

Nope. An easy solution (both here and for clang) is for ninja to set an environment variable (`NINJA_ISATTY`?), and add some magic to LLVM's "isatty" to return true if it sees it. (for matters of correctness, it would actually be best if ninja sets the environment variable only when *it's* stdout/stderr isatty (also taking into account this environment variable), so that

It is $target dependent. I’m curious what makes you think it is $host dependent. Thanks, Taewook On 3/3/17, 5:10 PM, "Jonathan Roelofs" <jonathan at codesourcery.com> wrote: On 3/3/17 12:23 PM, Taewook Oh wrote: > Thanks Jon. Actually I tried “x86_64-linux”, but it makes the test “Unsupported” from my linux machine, and it was because my test is under

On 9/8/14, 12:39 PM, Greg Fitzgerald wrote: > Hi Jon, > > Compiler-rt, libcxx, libcxxabi should all use the same > cross-compilation testing strategy. Compiler-rt already has a working > solution. If it is inadequate for libcxx or libcxxabi, can we start > by addressing those deficiencies? One issue to start with is that none of the libcxx/libcxxabi tests have RUN lines. All

Hi. I just want to know does anyone has the same problem or not. After running "make check-lit" tests are stopped at 61th percent (Linker tests). Each time it stops on different tests. Thanks. -- Regards, Stepan

So I started prototyping remote testing for libcxx over the weekend: https://github.com/jroelofs/libcxx/tree/remote_test The SSHExecutor isn't quite finished yet, but this should give an idea of what I've got in mind. Does this look generic enough to work for other projects under the llvm-umbrella (LNT, test-suite, compiler_rt, libcxxabi, etc)? Are there use cases that you see

Dan/Daniel/Eric, I'm testing a bare-metal ARM toolchain, and I've hacked up my local copy of lit to get it to run libcxx tests on qemu. I wanted to pick your collective brains to see if there was a better way of doing this. What I have implemented is here (don't take this as a formal review request, we can do that later once we figure out the best direction to go): lit part:

Hello, LLVM community. I've built a cross-toolchain on Windows and I'm now trying to run unit tests for the LLVM libraries. I used Ninja as a build system and MSVC as host compiler without an issue, but when I try to run 'ninja check-llvm-unit', I get the following error: llvm-lit.py: C:/Users/sergej/Developer/llvm-project/llvm\utils\lit\lit\TestingConfig.py:102: fatal: unable

On 9/8/14, 3:31 PM, Greg Fitzgerald wrote: > Jon, > >> One issue to start with is that none of the libcxx/libcxxabi tests have RUN lines. > > Sorry, I didn't mean to imply that 'RUN:' lines should be added to > libcxx tests. It's fine that every one is implicitly: > > // RUN: %clang %s -o %t && %run %t > ... and then when an explicit

llvm-lit is already put into <output-tree>/bin by CMake. There is a CMake target called `llvm-lit` that will generate the <output-dir>/bin/llvm-lit script. If you built only a few specific llvm targets such as FileCheck, etc then you may need to run this lit target manually. If you just run "ninja" for example, or "ninja check-llvm", it's automatically

Hm... tests were corrected themselves. No svn updates was made. 0. I turned on my laptop and boot Ubuntu 11.04. 1. I run ../llvm/configure in clean folder. 2. make 3. make check-lit 4. Tests was looped at 61%. Eclipse doesn't want to debug it too. It crashes at the start of debug session. I reboot my computer again, and all work well now. Probably some specific bios + OS + (specific cpu

Hi, Me and my supervisor are interested in improving llvm's lit a little bit. Currently, there are few things, that seem to be not very convenient about the tool: * Having several RUN commands in a failing test, it's impossible to figure out, which of them actually caused the test to fail. We can output the number of the failing RUN line. * It would be nice to