similar to: [LLVMdev] Nightly tester server down?

I've noticed that my nightly tester doesn't seem to be reporting the results of running llvm-test, only build warnings and make check. Checking with -verbose shows that it's running the test suite, so I don't quite understand what's going on. Looking at http://llvm.org/nightlytest/ shows that none of the other Linux testers are reporting test suite results either.

Hard to tell what's wrong. Perhaps /usr/local/bin is not part of path for a cron job? You should add NewNightlyTest.pl -noremove -release options. That leaves the build directory around for you examine it afterwards. Just manually delete the build directory before running NewNightlyTest.pl. Evan On Jul 20, 2008, at 6:00 PM, Nick Lewycky wrote: > I've noticed that my nightly

On Feb 16, 2008, at 2:35 PM, Tanya Lattner wrote: > On Feb 16, 2008, at 12:55 PM, Dale Johannesen wrote: >>> Using built-in specs. >>> Target: i686-apple-darwin9 >>> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ >>> src/configure --disable-checking --enable-werror --prefix=/ >>> Developer/ >>> usr/llvm-gcc-4.2

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: >>>

Nightly tester 'grawp' is reporting compilation error ? How do I see detailed build log ? Thanks, - Devang

hi all, After having some discussions in the IRC, I am trying here to come up with a proposal for GSoC 2008 for improving the llvm nightly tester[1].Following are the ideas and suggestions that came up in the discussion, if you have any comment or any other suggestion please add them to the list. I have some doubts in some places. 1. Improvements to the perl script which manage actual testing

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

> > Using built-in specs. > Target: i686-apple-darwin9 > Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ > src/configure --disable-checking --enable-werror --prefix=/Developer/ > usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man -- > enable-languages=c,objc,c++,obj-c++ --program-prefix=llvm- --program- >

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?

On Feb 16, 2008, at 12:55 PM, Dale Johannesen wrote: >> >> Using built-in specs. >> Target: i686-apple-darwin9 >> Configured with: /tmp/llvmgcc42.r46865.roots/llvmgcc42.r46865~obj/ >> src/configure --disable-checking --enable-werror --prefix=/Developer/ >> usr/llvm-gcc-4.2 --mandir=/Developer/usr/llvm-gcc-4.2/share/man -- >>

Hi Jeff, On Tue, 2007-01-02 at 20:17 -0800, Jeff Cohen wrote: > So when will the public mirror be updated? That version of llvm-gcc > still doesn't have the patch. It could be a while. Apparently the machine that ran the nightly job had a disk failure and some of the cron jobs etc are dead. The commits have been made on Apple's internal SVN server but haven't made it to the

Most of them should already be in our nightly tester. I went through the Alioth tests A while back and added them. -Owen Sent from my iPhone On Dec 15, 2008, at 5:03 PM, Evan Cheng <evan.cheng at apple.com> wrote: > FYI. http://leonardo-m.livejournal.com/73732.html > > If anyone is motivated, please file bugs for the losing cases. Also, > it might make sense to incorporate

> > 4. Running Fortran, Ada, C/C++/ObjC tests as well with test results emailed > > to the llvm-testresults. > > Are these different or new tests? Why wouldn't they just be a part of the > llvm-test module? Then you don't have to do any modifications to the > scripts. Probably means the gcc testsuite. Ciao, Duncan.

On Mon, 2007-01-01 at 00:44 -0800, Evan Cheng wrote: > Ok, so I guess the issue is llvm-gcc has to be updated. There are > some issues with the Apple svn repository so I checked out a copy > from the public mirror. Looks the latest patch hasn't made it through: Yeah, it should have just made it througha couple hours ago, but not at the time of your writing this email. Reid.

Rajika, A couple of comments: - You should provide a way to specify where llvm-gcc is built (just like llvm). - I would highly recommend allowing the user to only update llvm-gcc and not check it out from scratch each time. Checking out llvm-gcc is very time consuming. You would need to make sure that llvm and llvm-gcc have the same rev number and nuke the llvm obj/install dirs so you get a

Hello, On Jun 3, 2008, at 08:52 , Tanya Lattner wrote: > 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. I think I might be able to set up a nightly tester for Linux x86 (32- bit). Although I've been following LLVM for

hello every body. Here with I have attached the patch which compile the llvm-gcc using nightly tester script. This patch add the following capabilities to the NewNightlyTester.pl script. 1. Checkout the llvm-gcc4.2 source from the SVN. 2. Compile the checkout llvm-gcc4.2 source tree. 3. Gather the configure/make out put informations. 4. Add the (3) informations to the %hash_of_data hash to be

Yes, they are real. I re-ran the two tests with the biggest execution time regressions, and the results were completely reproducible. On Oct 12, 2011, at 1:24 AM, Duncan Sands wrote: > Hi Bob, are these performance regressions real? They look pretty serious. > > Ciao, Duncan. > > On 10/12/11 09:40, llvm-testresults at cs.uiuc.edu wrote: >> >>

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

Hi Chris, > Can you check to see if the stepanov_container/fftbench regressions > are real? If so, it would be very interesting to know what is "going > wrong" on them. I think these may not be real. This version of llvm-gcc was built with checking enabled - does this turn on checking in libstdc++? It seems that a bunch of linkonce libstdc++ checking code is now being