similar to: [LLVMdev] NightlyTest Broken?

Reid Spencer wrote: > It seems after the change on Zion that the nightly test is broken. When > I go to http://llvm.org/nightlytest/, I get a blank page. Any ideas? > According to the web server error log, there's a syntax error in the PHP script for that page. It looks like Patrick Jenkins made some changes earlier today (aka last last night). This is the error that I get:

Reid Spencer wrote: 1) It appears that the only problem was with sending email to the llvm-commits list; any files commited to the repository should be commited. 2) The web server error log filled up /var/log, preventing the CVS commit script from sending email. The Apache error log was filled with entries like this: [client 219.140.157.109] PHP Notice: Undefined offset: 1 in

How big was that log file? If we are running close to the limit, I can just buy a new disk for zion. Other suggestions welcome. --Vikram On Nov 25, 2006, at 12:38 AM, John T. Criswell wrote: > Reid Spencer wrote: > > 1) It appears that the only problem was with sending email to the > llvm-commits list; any files commited to the repository should be > commited. > >

All, Commits aren't taking right now because apparently Zion is out of disk space: cvs commit utils/findmisopt Checking in utils/findmisopt; /var/cvs/llvm/llvm/utils/findmisopt,v <-- findmisopt new revision: 1.9; previous revision: 1.8 done Insufficient disk space; try again later Insufficient disk space; try again later returntosender: cannot select queue for llvm Insufficient disk

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > At this moment I use > "gmake TEST=nightly" command line to run night tester > > What I must specific and where to disable SPEC run (i don't have it) I think that it's currently a bug that this does not automatically happen. > I known about new NightlyTest.pl option: -noexternals > But what I must do for

> Are you using the NightlyTest.pl file? To run the tester I don't use > gmake directly at all. Instead, I have this in my crontab: > > 5 3 * * * LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan /home/vadve/shared/PublicCVS $HOME/buildtest-X86 $HOME/cvs/testresults-X86 > > When run like this,

At this moment I use "gmake TEST=nightly" command line to run night tester What I must specific and where to disable SPEC run (i don't have it) I known about new NightlyTest.pl option: -noexternals But what I must do for enable it Vladimir

> On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > > At this moment I use > > "gmake TEST=nightly" command line to run night tester > > > > What I must specific and where to disable SPEC run (i don't have it) > > I think that it's currently a bug that this does not automatically happen. > > > I known about new NightlyTest.pl option:

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > Are you using the NightlyTest.pl file? To run the tester I don't use > > gmake directly at all. Instead, I have this in my crontab: > > > > 5 3 * * * > LLVM_LIB_SEARCH_PATH=/home/vadve/lattner/local/x86/llvm-gcc/bytecode-libs > $HOME/llvm/utils/NightlyTest.pl -parallel -enable-linscan >

>> > I assume you're talking about the FreeBSD run. I'm not sure what is >> > going >> > on >> >> No. You can see problem with Feature tests at >> http://llvm.cs.uiuc.edu/testresults/X86/ also (see Feature Test Results >> section ) > > I'm not sure that I follow. The qmtest stuff isn't working on Zion > because (I

It's already messed with, but there's no harm. If someone turns on the llvm2cpp option, then they get an error message at the bottom of the output page. All other output is normal. So, there's no harm in it. If/when llvm2cpp becomes available on Zion, people then the llvm2cpp output will appear. Note that llvm2cpp is a 1.8 release feature. My change was to help people learning LLVM

The demo script isn't part of the release and its not failing. Do you want me to revert the changes? Reid. On Thu, 2006-08-10 at 10:08 -0700, Tanya M. Lattner wrote: > > It's already messed with, but there's no harm. If someone turns on the > > llvm2cpp option, then they get an error message at the bottom of the > > output page. All other output is normal. So,

Hello, I'm trying to get the demo script to run llvm2cpp so that people can get familiar with the LLVM C++ API through the online demo. However, it seems that the path used doesn't include llvm2cpp (not updated in a while?). The demo script currently uses these paths on Zion: /home/vadve/criswell/box/x86/llvm-gcc/bin/ /home/vadve/gaeke/llvm/Release/bin /home/vadve/gaeke/bin

> It's already messed with, but there's no harm. If someone turns on the > llvm2cpp option, then they get an error message at the bottom of the > output page. All other output is normal. So, there's no harm in it. > If/when llvm2cpp becomes available on Zion, people then the llvm2cpp > output will appear. Note that llvm2cpp is a 1.8 release feature. My > change was

> I'm trying to get the demo script to run llvm2cpp so that people can get > familiar with the LLVM C++ API through the online demo. However, it > seems that the path used doesn't include llvm2cpp (not updated in a > while?). The demo script currently uses these paths on Zion: I can look into this, but I would strongly suggest not messing with the demo script until 2-3

On Thu, 10 Aug 2006, Tanya M. Lattner wrote: >> The demo script isn't part of the release and its not failing. >> Do you want me to revert the changes? > No. I just said that we should avoid anymore changes for the next 2 weeks to > maintain stability. FWIW, I agree with Tanya on this. People *pound* on the demo page immediately after a release as they try it out and

Vladimir, Did the checkout fail? Its trying to do a chdir("llvm") in the build directory (second argument to the script) but that directory doesn't exist or isn't executable. Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm dir? Reid. On Thu, 2004-06-24 at 10:42, Vladimir Merzliakov wrote: > > Are you using the NightlyTest.pl file? To run the

> The demo script isn't part of the release and its not failing. > > Do you want me to revert the changes? No. I just said that we should avoid anymore changes for the next 2 weeks to maintain stability. -Tanya > > Reid. > > On Thu, 2006-08-10 at 10:08 -0700, Tanya M. Lattner wrote: >>> It's already messed with, but there's no harm. If someone turns on

>> I'm not sure that I follow. The qmtest stuff isn't working on Zion >> because (I believe) of an upgrade that happened on the machine (the >> qmtest >> binary doesn't work anymore?). Are you seeing a problem on freebsd where >> the feature tests go into a loop? If so, can you provide us with more >> information? >> make, ~ > ps -xu

Result night tester run at FreeBSD 5.1 accessable by URL http://npt.cc.rsu.ru/testresults-X86-FreeBSD/index.html I can't guaranty run it per day base, sorry. As i can see, make (bug 385) and perl (bug 386) not builded by NightlyTest.pl (but builded if use gmake night tests run format) So I don't known preferable solutions: its can be closed or patches applied. Vladimir