similar to: [LLVMdev] nightly tester setup

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

Daniel Dunbar wrote: > Did you manage to solve your issue yet, I just had the same problem > and found out that the problem was that I had redefined LLVMGCC > which was (eventually) causing LCC1 to get defined to garbage in Makefile.rules. > Since the .bc target depends on the source and LCC1 this was basically > breaking all the rules. I haven't fixed it yet, but I haven't

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

> x86 FreeBSD: > * hasn't run with changes yet I manually start script. I use this options (+ -verbose now for testing) /home/wanderer/pkg/build/llvm/src/llvm/utils/NightlyTest.pl -parallel -enable-linscan -noexternals -noremove :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm /home/wanderer/pkg/build/llvm/night/build

> 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

On Wed, Feb 25, 2009 at 10:26:02AM -0800, Chris Lattner wrote: > > On Feb 24, 2009, at 10:03 PM, Julien Lerouge wrote: > > > On Tue, Feb 24, 2009 at 06:24:17PM -0800, Julien Lerouge wrote: > >> I haven't tested with objdir != srcdir. > > > > Ok, that was broken. Attached is a smaller diff that should work in > > all > > cases. > > This

On Feb 24, 2009, at 10:03 PM, Julien Lerouge wrote: > On Tue, Feb 24, 2009 at 06:24:17PM -0800, Julien Lerouge wrote: >> I haven't tested with objdir != srcdir. > > Ok, that was broken. Attached is a smaller diff that should work in > all > cases. This sounds really cool Julien! Two questions: 1) does it preserve the checking that the existing tcl stuff does, which

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

The utils/NewNightlyTest.pl script seems to use LLVMGCCDIR in a way that is inconsistent with the top-level configure script. I would like to fix this but I don't want to break everyone's nightly tests. Can someone review the attached patch to make sure I'm not missing something? The NewNightlyTest.pl script checks the LLVMGCCDIR environment variable and uses it for two

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

My main complaints about the nightly tester are: Loading the web pages is waaay tooo sllooooow The information provided is not terribly useful for tracking down bugs. What bug fixers need is environment+command line options adequate to reproduce the problem. Access to the run logs would be a good start. On Apr 4, 2008, at 9:22 PM, Rajika Kumarasiri wrote: > hi all, > After having

Hi Devang, Unfortunately, there's no way to see the build log unless you're on the machine from which the report was generated. If you can log in to Grawp's machine then it should be in the "WEBDIR". It is most likely mis-compiling because the needed llvm-gcc patch has not been applied after the SETCC patch to LLVM was committed last weekend. Reid. On Fri, 2006-12-29 at

On Wed, Feb 25, 2009 at 12:02:18PM -0800, Julien Lerouge wrote: > For 2), I think the NewNightlyTest.pl script would require some small > changes, to invoke the jcheck target instead of check, pass the desired > -j flag, and also parse the log. I'll take a look. In any case, the > changes would only apply to the DejaGNU tests (llvm-test already works > fine with -jX). Here is

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

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

After the removal of llvm/test/Programs and insertion of llvm-test cvs module, the nightly tester showed the following: x86 Linux debug: * hard to say. I think it failed because the check in occurred just as it was starting up. Could someone verify for me? No results were produced. x86 Linux optimized: * everything ran okay * loc graph now shows 550k lines (up 350k!) - not sure

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

> 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

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

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