similar to: [LLVMdev] Update To Optimized Nightly Test

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, ] >

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

Reid, Click on any of these logs and you'll see the same asm parsing issues. It's been going on for much of the week. http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt http://llvm.org/nightlytest/machines/2006-12-29_05:40:12-Build-Log.txt llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build (bytecode)

Jim Laskey wrote: > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build > (bytecode) > /Volumes/Muggles/LLVM/nightlytest/build/llvm/Release/bin/gccas: / > Volumes/Muggles/LLVM/nightlytest/build/llvm/projects/Stacker/lib/ > runtime/Release/stacker_rt.ll:21,0: parse error, expecting `LOAD' or > `STORE' >

Hey All, I have been making some changes to the nightly tester that will hopefully make debugging problems and performance issues easier. The big change is nightly test results will now be kept in a central location (http://llvm.org/nightlytest/index.php). I have committed a new file to utils/ called 'NewNightlyTest.pl'. It *should* behave almost exactly like the previous NightlyTest.pl

You all just need remove "stacker_rt.ll". the stacker_rt.ll is a generated file, not source. The Makefile should have a dependency on llvm-gcc for it, but doesn't. Just remove stacker_rt.ll and the problem will go away. Reid. On Sat, 2006-12-30 at 08:37 -0500, Nick Lewycky wrote: > Jim Laskey wrote: > > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build

FYI: It also showed up for ARM yesterday, but only for a non-debug build. On Mar 5, 2009, at 4:32 AM, Gabor Greif wrote: > Hi Bill, > > this might be a latent bug related to PPC. I have no such > machine to access atm., but I shall be able to reproduce the > problem when back at home. (In about 4 hours). > > I keep you informed. > > Cheers, > > Gabor >

On May 30, 2008, at 4:34 AM, Apache wrote: > http://llvm.org/nightlytest/test.php?machine=277&night=6245 > Name: grue.apple.com > Nickname: grue-x86-64-pic > Buildstatus: Error: compilation aborted > > Buildlog available at http://llvm.org/nightlytest/machines/2008-05-30_06:33:56-Build-Log.txt That last pathname is not correct, it should be

Hi Bill, this might be a latent bug related to PPC. I have no such machine to access atm., but I shall be able to reproduce the problem when back at home. (In about 4 hours). I keep you informed. Cheers, Gabor On Mar 4, 7:57 pm, Bill Wendling <wendl... at apple.com> wrote: > Something last night broke the build on Darwin PPC. Possible Gabor's   > check-in? > > -bw

Would those of you running the nightly tester make sure they are using the NEW default script "/nightlytest/ NightlyTestAccept.php" (was /nightlytest/NightlyTestAccept.cgi",) This would require that you have an updated llvm/utils/ NewNightlyTest.pl and that you are not overriding with a different script using -submit-script=. Thank you. Cheers, -- Jim --------------

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 /

Something last night broke the build on Darwin PPC. Possible Gabor's check-in? -bw Begin forwarded message: > From: admin at spang.apple.com (admin) > Date: March 4, 2009 3:56:10 AM PST > To: wendling at apple.com > Subject: PPC Nightly Build Result > > /Volumes/SandBox/NightlyTest/llvmgcc42.roots/llvmgcc42~obj/obj- > powerpc-powerpc/./prev-gcc/xgcc

Aaron Gray wrote: > It would be good to have a mailing list for test results where 'make check' > results could be posted so that there is some reference and people could > avoid repeating builds. There's the llvm-testresults list, but I find it less than fully useful because it's not immediately obvious from scanning message subjects if there's been a test

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

We are experiencing serious load/memory issues on llvm.org and unfortunately, there is not anything we can do about it. This means that because the nightlytest page needs to access a mysql database, it will be very very slow. Bugzilla will be slow too. We have a machine being ordered, but it will take time to arrive and time to setup. Until then, I'm asking people to please try to be

On Thursday 23 July 2009 17:43, Tanya Lattner wrote: > We are experiencing serious load/memory issues on llvm.org and > unfortunately, there is not anything we can do about it. This means > that because the nightlytest page needs to access a mysql database, it > will be very very slow. Bugzilla will be slow too. Has there been a spike in traffic recently? Or maybe I just got lucky

On Wed, 2006-10-18 at 12:43 -0700, Chris Lattner wrote: > On Wed, 18 Oct 2006, Reid Spencer wrote: > > I had upgraded my Linux kernel from 2.6.17 to 2.6.18. I suggested to Jim > > that changes in the minor revision number of the operating system should > > not count as a new machine. He said he'd look into it when he has time. > > Its not a huge issue, I just

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

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.

This is just a note to point out that LLVM now has a automated nightly regression test suite. The results of which are here: http://llvm.cs.uiuc.edu/testresults/ The script is checked into CVS in the utils/NightlyTest* files. This is meant to keep track of the progress LLVM makes with bug fixes, and help ensure that LLVM get more solid as it is developed, not more fragile. Currently we only