similar to: [LLVMdev] Problems with nighttest FeatureTests

Vladimir Merzliakov wrote: > Hi! > > As I can see all nighttesters listed at > http://llvm.cs.uiuc.edu/testresults/ have problem with > FeatureTests at 2004-11-01/2004-11-02 test run. > > In my case i manualy terminate nighttest script after 12 hours work. > > It problem resolved? > > Vladimir Hi Vladimir, I assume you're talking about the FreeBSD run.

> Vladimir Merzliakov wrote: > >> Hi! >> >> As I can see all nighttesters listed at >> http://llvm.cs.uiuc.edu/testresults/ have problem with >> FeatureTests at 2004-11-01/2004-11-02 test run. >> >> In my case i manualy terminate nighttest script after 12 hours work. >> >> It problem resolved? >> >> Vladimir > > Hi

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

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

I think there is a very similar situation with the PowerPC/Mac OS X nightly tests. Over each of the past few nights, something has been filling up the process table, causing me to be unable to log in. The nightly tester wrote out regression test and feature test logs featuring hundreds of "Resource temporarily unavailable" errors from fork(), so I assume it's the qmtest

Just for information. After root update OS from FreeBSD 5.1 to FreeBSD 5.3-RC1 at make.cc.rsu.ru I don't rebuild LLVM C Frontend. Last LLVM build fail (2004-10-30) is result this situation. I update LLVM C Frontend and rerun manually nighttest script. All ok now :) Also, I think, "X86: FreeBSD 5.1 (may not be run every day)" line at

On Wed, 3 Nov 2004, Vladimir Merzliakov wrote: > >> It problem resolved? > >> > >> Vladimir > > > > Hi Vladimir, > > > > 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

A typo in test/Makefile was the trigger for this problem: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ 020216.html John, can you please look into this bug some more and add some error checking to the llvm-specific qmtest python modules to make this error less severe? Thanks! -Brian On Nov 3, 2004, at 10:35 AM, Brian Gaeke wrote: > > I think there is a very

Brian Gaeke wrote: > > A typo in test/Makefile was the trigger for this problem: > > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ > 020216.html > > John, can you please look into this bug some more and add some error > checking to the llvm-specific qmtest python modules to make this error > less severe? Does the fork bomb occur in the

After fixing nested () problem manual run nighttest finished successfully with one remarkable logged problem: INITIALIZED CVS Root = :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm BuildDir = /home/wanderer/pkg/build/llvm/night/build WebDir = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD Prefix = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD/2004-09-06

> Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm dir? After providing :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm at CVSROOT this problem disappear. But have personal problem: I must have now 2 copy LLVM sources 1) to plain build llvm 2) to nighttester run Can I use llvm builded in nighttest/build directory to install plain llvm? Vladimir

Okay, I'll have to fix NightlyTest.pl not to use shell script syntax that isn't universal. Look for a commit soon. Reid. On Sun, 2004-09-05 at 13:31, Vladimir Merzliakov wrote: > > Bash 2.05b on Linux handles this fine. I was asking what > > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > > Perhaps you can: > > > >

> That's weird. What is your default shell that Perl invokes with the > "system" command. This works fine with bash-2.05b. In reality :) i use this script in crontab (and run it manually with added verbose flag): ---8X-------------- #!/bin/sh - # if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ]) then mkdir

That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >

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

>I successfully build CFE frontend at FreeBSD 5.3. > > Next nighttest run show more detail information :) After last 2 nighttest runs i see stable failure result: llvm[2]: Compiling dummylib.c for Debug build (bytecode) llvm-g++: installation problem, cannot exec `gccas': No such file or directory gmake[3]: ***

> Only thing I can think of is that your "platform" link is missing. > make sure "platform is a symbolic link to your platform's subdirectory > in the llvm/lib/System directory. If you're on FreeBSD then: > > ln -s FreeBSD platform > > this should have been done for you when you configured. My fault. I make cvs update llvm and AFTER remove build

>> All SingleSource and MultiSource tests failed in last run of FreeBSD >> nighttester (and in previous). >> Mostly with error: > > This looks like your crtend.a file did not get built correctly. Try doing > make clean/make install in llvm/runtime/ again. > gmake clean in llvm/runtime/ remove all build tree of nighttest starting with llvm/runtime/../.. And then i

Next problem detected by nighttest: LLVM build fail with errors: gmake[4]: Entering directory `/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime' llvm[4]: Compiling stacker_rt.c for Debug build (bytecode) default/bin/llvm-gcc: not found gmake[4]: *** [/usr/home/wanderer/pkg/build/llvm/night/build/llvm/projects/Stacker/lib/runtime/Debug/stacker_rt.bc] Error 1

On Thu, 24 Jun 2004, Vladimir Merzliakov wrote: > > Can you verify that you have an $HOME/pkg/build/llvm/night/build/llvm > dir? > > After providing :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm at > CVSROOT > this problem disappear. > > But have personal problem: I must have now 2 copy LLVM sources > 1) to plain build llvm > 2) to nighttester run >