search for: testingguide

Thanks Duncan, I figured it out after a couple of tries, but the docs are not as clear as your instructions. If there's no specific maintainer of TestingGuide.html, I'd be happy to update the docs to be as clear as your instructions. llvm/projects/Makefile filters out "test-suite" and "llvm-test" when builds are done, so it looks like those two names work. John On Sat, Mar 28, 2009 at 2:35 PM, Duncan Sands <baldrick at free....

How do I get the LLVM test-suite to work I have followed the /docs/TestingGuide.html but cannot seem to get it to work. I have tried many variations, but get no joy. The docmunetation does not appear very clear. Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090328/e15c2e57/attac...

On Thu, Jan 17, 2013 at 1:30 PM, Eli Bendersky <eliben at google.com> wrote: > This is unfortunate. Last month I tweaked TestingGuide.rst to > discourage grep in favor of FileCheck. It now says: > > "The recommended way to examine output to figure out if the test > passes it using the FileCheck tool. The usage of grep in RUN lines is > discouraged." > > However, perhaps it's time to remove any m...

All, We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform. Directions to set up a tester are here: http://llvm.org/docs/TestingGuide.html#nightly These directions could be improved of course. If you have any questions, I will be happy to assist you in setting up your nightly tester. Thanks! -Tanya

...> `FileCheck` an error. >> >> I think that within a month this knowledge will be propagated to all developers. > > I'd like to think so, too, but we still get patches that write tests using 'grep' instead of FileCheck. > This is unfortunate. Last month I tweaked TestingGuide.rst to discourage grep in favor of FileCheck. It now says: "The recommended way to examine output to figure out if the test passes it using the FileCheck tool. The usage of grep in RUN lines is discouraged." However, perhaps it's time to remove any mention of grep from that document...

...from /lib64/libc.so.6 #29 0x0000000000000000 in ?? () 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it isn't completely obvious how to run the test-suite using clang rather than llvm-gcc. I've made a couple stabs at it without success. If there is new documentation that I've missed, please be kind when you...

Hi Aaron, > How do I get the LLVM test-suite to work I have followed the /docs/TestingGuide.html but cannot seem to get it to work. I have tried many variations, but get no joy. The docmunetation does not appear very clear. (1) check out the testsuite. The default name of the checkout is "test-suite". (2) move it into llvm/projects/, changing the name to llvm-test, so now you...

> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it isn't completely obvious how to run the test-suite using clang rather than llvm-gcc. I've made a couple stabs at it without success. If there is new documentation that I've missed, please be kind when you...

From http://llvm.org/docs/TestingGuide.html Some tests are known to fail. Some are bugs that we have not fixed yet; others are features that we haven't added yet (or may never add). In DejaGNU, the result for such tests will be XFAIL (eXpected FAILure). In this way, you can tell the difference between an expected and unexpected...

...任 <chenwj at iis.sinica.edu.tw> writes: >> 2) I had no problem running the V3.0 regression tests according to the instructions. However, the instructions in the Testing Infrastructure Guide for running the Test Suite presume the existence and use of llvm-gcc, http://llvm.org/docs/TestingGuide.html, both on-line and in the rc4 kits. Now that llvm-gcc is gone for V3.0, it isn't completely obvious how to run the test-suite using clang rather than llvm-gcc. I've made a couple stabs at it without success. If there is new documentation that I've missed, please be kind when you...

On Jan 17, 2013, at 9:57 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: > On Thu, Jan 17, 2013 at 7:51 PM, Sean Silva <silvas at purdue.edu> wrote: >> On Thu, Jan 17, 2013 at 8:36 AM, Dmitri Gribenko <gribozavr at gmail.com> wrote: >>> We have to options: >>> (a) replace 'FileCheck' with '%FileCheck' in all tests, and teach

2009/3/28 John Mosby <ojomojo at gmail.com> > Thanks Duncan, > I figured it out after a couple of tries, but the docs are not as clear as > your instructions. If there's no specific maintainer of TestingGuide.html, > I'd be happy to update the docs to be as clear as your instructions. > > llvm/projects/Makefile filters out "test-suite" and "llvm-test" when builds > are done, so it looks like those two names work. > > John > > On Sat, Mar 28, 2009 at 2:35...

...ls above it, so I moved >> llvm-suite into the "test" subdirectory inside the llvm compiler >> checkout. I ran "make" again, but I got this: >> > > You need to put it under the "projects" subdirectory. Read this: > http://llvm.org/docs/TestingGuide.html > > It is perhaps a little confusing; looks like you stopped reading after > the first "test suite" section. Keep going. > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu...

Please, can anybody show me the required steps for running the LLVM regression tests, or point me to a detailed doc? I read the available documentation in https://llvm.org/docs/TestingGuide.html <https://llvm.org/docs/TestingGuide.html> but that's mostly a general description on what’s available rather than an “guide”. This is what I tried: - Installed both LLVM and CLANG using CMAKE on a Mac OS X computer. (Sources compiled fine, and everything seems to work as I’m alre...

Hi, I'm trying to run the benchmark suite: http://llvm.org/docs/TestingGuide.html#test-suite-quickstart I'm doing it the lnt way, as described at: http://llvm.org/docs/lnt/quickstart.html I don't know what to expect but the results seems to be quite noisy and unstable. E.g I've done two runs on two different commits that only differ by a space in CODE_OWNE...

...there not being a Makefile two levels above it, so I moved > llvm-suite into the "test" subdirectory inside the llvm compiler > checkout. I ran "make" again, but I got this: You need to put it under the "projects" subdirectory. Read this: http://llvm.org/docs/TestingGuide.html It is perhaps a little confusing; looks like you stopped reading after the first "test suite" section. Keep going.

On Mar 28, 2009, at 2:17 PM, John Mosby wrote: > Thanks Duncan, > > I figured it out after a couple of tries, but the docs are not as > clear as your instructions. If there's no specific maintainer of > TestingGuide.html, I'd be happy to update the docs to be as clear as > your instructions. > Please! :-) Maybe the wiki too. -bw > llvm/projects/Makefile filters out "test-suite" and "llvm-test" when > builds are done, so it looks like those two names work. >

From http://www.llvm.org/docs/TestingGuide.html#quickdejagnu : To run only a subdirectory of tests in llvm/test using DejaGNU (ie. Transforms), just set the TESTSUITE variable to the path of the subdirectory (relative to llvm/test): % gmake TESTSUITE=Transforms check On 17-Jun-09, at 1:33 PM, Aaron Gray wrote: > Does 'make ch...

FYI, this was commonly requested, enjoy: http://llvm.org/docs/TestingGuide.html#FileCheck-Matching -Chris

On Jul 22, 2010, at 2:44 PMPDT, Patrick Alexander Simmons wrote: > From http://llvm.org/docs/TestingGuide.html > > Some tests are known to fail. Some are bugs that we have not fixed > yet; > others are features that we haven't added yet (or may never add). In > DejaGNU, the result for such tests will be XFAIL (eXpected FAILure). > In > this way, you can tell the difference...