similar to: [LLVMdev] inconsistent use of LLVMGCCDIR?

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

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

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

> I've run the test last night to see how long it takes, and I can > afford to cronjob it for the night. Great! > I didn't quite realize it would automatically send the report, but > it did [1] and there are a few test failure from the > Frontend{C,C++} directories. I suppose this is because I have > llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is >

As part of trying to fix PR30610 (ThinLTO with module inline asm), I wanted to add an assert that we have a Target and an MCAsmParser when we have non-null module inline asm in IRObjectFile::CollectAsmUndefinedRefs. Otherwise it silently fails to parse the module inline asm, which I initially found when trying to add an 'opt' based test for my fix (because 'opt' wasn't

> 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

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

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

Hello list! Tanya Lattner wrote: > 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've run the test last night to see how long it takes, and I can afford to cronjob it for the night. I didn't quite realize it would automatically

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

All, I know we've cried wolf before, but the conversion of the LLVM projects' software to use Subversion instead of CVS *WILL* occur on Friday June 29th with the following approximate schedule: * 09:00 CDT (14:00 UTC, 07:00 PDT) - CVS becomes read-only (commits prevented) * 09:05 CDT (14:05 UTC, 07:05 PDT) - Final conversion to SVN starts * 11:45 CDT

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

On Tue, 26 Jun 2007, Reid Spencer wrote: > I know we've cried wolf before, but the conversion of the LLVM projects' > software to use Subversion instead of CVS *WILL* occur on Friday June > 29th with the following approximate schedule: Great, I'm glad to see this happening. Thanks for making it happen. One request: when the change goes live, please make sure the various

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

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, Apparently there are two bugs in tools/llvmc/c: /.../llvm/tools/llvmc/c:12: Error: Invalid top level configuration item /.../llvm/tools/llvmc/c:28: Error: Expecting a program name /.../llvm/tools/llvmc/c had 2 errors. Terminating. The first error relates to the following line(s): lang.libs=%llvmgccdir%/lib %llvmgccdir%/lib \ %llvmgccdir%/lib/gcc/%llvmgccarch% ... the other one to:

On Feb 19, 2005, at 20:26, Reid Spencer wrote: > You need to tell configure where the install directory for all of > llvm-gcc is located. Ah ha. That was my problem. I forgot that I ran into this with LLVM 1.4 as well. Basically, I specified: --with-llvmgccdir=/Users/ejones/llvm/cfrontend/ppc/llvm-gcc/bin instead of: --with-llvmgccdir=/Users/ejones/llvm/cfrontend/ppc/llvm-gcc Which

Am Samstag, den 08.03.2008, 15:11 -0800 schrieb Tanya Lattner: > >> A -noreport option is probably a good idea too. > > > > OK, that should be easy to add. > > > >> Just be sure not to change what it sends to the website. That needs > >> to > >> stay the same. > > > > Sure. I think wrapping an if statement around the HTTP send