similar to: [LLVMdev] 2 experimental projects

>> 1) Parallel "make check". >> Modelled after the successful clang "make test -jX" experiment, I am >> now bold enough to sink my teeth into the LLVM test suite. >> I have a prototype implementation, along the same lines, ready. > >Can you please explain this in detail. > >Thanks, >Tanya Sure. This is how "make test

On Oct 18, 2009, at 7:49 PM, Daniel Dunbar wrote: > Hi all, > > As you may or may not have noticed, I have gradually been replacing > the testing infrastructure in LLVM. Most of this work is moving LLVM > and Clang to share a single testing tool, 'lit'. See: > http://llvm.org/cmds/lit.html > for documentation on the tool itself. > > If you haven't already

It's me. Our ISD::LABEL implementation has issues... Evan On Jan 30, 2008, at 9:34 PM, Dale Johannesen wrote: > > On Jan 30, 2008, at 9:12 PM, Apache wrote: > >> http://llvm.org/nightlytest/test.php?machine=231&night=4754 >> Name: il0102a-dhcp80.apple.com >> Nickname: OldGrawp-O0-PIC >> Buildstatus: OK >> >> New Test Passes: >>

On Thu, 10 Mar 2005, Vladimir Merzliakov wrote: >> Do to popular request, I just set up a new mailing list to capture the >> nightly tester output from the various testers running 'round the world. >> The new list is available here: >> http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults >> >> If you're running a nightly tester, please update

On Feb 16, 2008, at 11:32 AM, Evan Cheng wrote: > But I am using llvm-gcc-4.2. Any idea why it's failing? > > Evan All the failing testers are using gcc-4.0 according to the web pages they point at. > On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > >> On Feb 16, 2008, at 7:06 AM, Apache wrote: >>> New Test Failures: >>>

Hi all, As you may or may not have noticed, I have gradually been replacing the testing infrastructure in LLVM. Most of this work is moving LLVM and Clang to share a single testing tool, 'lit'. See: http://llvm.org/cmds/lit.html for documentation on the tool itself. If you haven't already tried it, please consider switch to 'make check-lit' as an alternative to 'make

llvm itself is built with gcc-4.0, but the run line is: // RUN: %llvmgxx -S -O0 -emit-llvm %s -o - | grep retval | grep S242 | grep {i32 1} | count 2 According the log: FAIL: /Volumes/Muggles/LLVM/nightlytest-pic/build/llvm/test/C+ +Frontend/2008-02-13-sret.cpp Failed with exit(1) at line 1 while running: /usr/local/bin/llvm-gcc -emit-llvm -S -O0 -emit-llvm /

On Wed, 2005-02-16 at 19:52, Aaron Gray wrote: > Hi Reid, > > I'll send a complete report tommorow, its getting late. Great! > > It looks like there is alot of work to do to get the MS VC version in line > with the Unix release. I am very willing to help out with porting. Yes, there are several well known issues remaining. The bugpoint tool and the debugger use unix

> Do to popular request, I just set up a new mailing list to capture the > nightly tester output from the various testers running 'round the world. > The new list is available here: > http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults > > If you're running a nightly tester, please update your crontab to send > mail to the llvm-testresults at cs.uiuc.edu list

On Feb 16, 2008, at 7:06 AM, Apache wrote: > New Test Failures: > test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU] This test doesn't work with gcc-4.0, which caused it to fail on a number of testers overnight. I can fix that in 4.0, but as I understand it we're going to drop support for it next release, so how about now?

> > Cons of QMTest: > > 1) You have to use the gui to add directories. > > I think you're wrong. Manually creating a directory would work, as QMTest does > not place anything special in directories. I may have worded this poorly, but I think you have to use the gui to add new directories or tests, or specific tests. Otherwise, it does not know what to do with those

Hi All, Do to popular request, I just set up a new mailing list to capture the nightly tester output from the various testers running 'round the world. The new list is available here: http://mail.cs.uiuc.edu/mailman/listinfo/llvm-testresults If you're running a nightly tester, please update your crontab to send mail to the llvm-testresults at cs.uiuc.edu list (potentially in addition

On Jan 30, 2008, at 9:12 PM, Apache wrote: > http://llvm.org/nightlytest/test.php?machine=231&night=4754 > Name: il0102a-dhcp80.apple.com > Nickname: OldGrawp-O0-PIC > Buildstatus: OK > > New Test Passes: > test/CFrontend/2008-01-28-PragmaMark.c [DEJAGNU] > > > New Test Failures: > Benchmarks/Shootout-C++/except [LLC compile, ] >

But I am using llvm-gcc-4.2. Any idea why it's failing? Evan On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > On Feb 16, 2008, at 7:06 AM, Apache wrote: >> New Test Failures: >> test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU] > > This test doesn't work with gcc-4.0, which caused it to fail on a > number of testers overnight. I can fix that in 4.0, but as I

Can any one, who has dejagnu and expect installed and working, send me an output when running '(g)make check' from llvm. Thanks. Henrik. ============================================================= Henrik Bach LLVM Open Source Developer e-mail: henrik_bach_llvm at hotmail.com ============================================================= 'Nothing is impossible; The impossible

On Jan 28, 2009, at 8:25 PM, Tanya Lattner wrote: > On Jan 28, 2009, at 3:46 PM, David Greene wrote: > >> On Wednesday 28 January 2009 15:59, Tanya Lattner wrote: >>> On Jan 28, 2009, at 12:18 PM, David Greene wrote: >>>> I have a buildbot operating to do validating builds of llvm up at >>>> >>>> http://obbligato.org:8080 >>>>

Hi all, I have two llvm projects in different stages of execution: 1) Parallel "make check". Modelled after the successful clang "make test -jX" experiment, I am now bold enough to sink my teeth into the LLVM test suite. I have a prototype implementation, along the same lines, ready. 2) <class Use> size reduction. After some conversation with Chris I think we are ready

Dear list, I have a vector of characters and a list of two named elements : i <- c("a","a","b","b","b","c","c","d") j <- list(j1 = c("a","c"), j2 = c("b","d")) I'm looking for a fast way to obtain a vector with names, as follows : [1] "j1" "j1"

> > Ah! This is the one that's messing up. Could someone take a look at > this and see why it's failing? It doesn't even seem to be getting to > the "svn" checkout. > > Hi Bill, [sorry I was not subscribed to llvm-testresults, and noticed this only now] This is a buildbot bug apparently, see http://buildbot.net/trac/ticket/284 and

In an effort to simplify how tests are added to the LLVM testsuite, I've added support for Dejagnu. This only applies to the Feature and Regression tests. If this experiment goes well, we may switch from using QMTest to Dejagnu. I'm asking for people (especially those running nightly testers) to give Dejagnu a try. You will need to install Dejagnu (http://www.gnu.org/software/dejagnu/)