similar to: [LLVMdev] Trying to set up a nightly test

Hi all again, llvm is failing the 2006-11-30-NoCompileUnit and 2006-11-30-Pubnames tests on me. -m32 and --disable-multilib didn't change the outcome. Did I get the command wrong? I tried jo at kurier:~/Delta/llvm/test$ CFLAGS=--multilib make check See below for a transcript of the failed check. What next? Regards, Jo -- snip -- jo at kurier:~/Delta/llvm/test$ make check llvm[0]:

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

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

Hi all, I found enough to explain the behaviour that I encountered. If I'm correct, the bugs are just in the dejagnu-based test machinery, not in LLVM itself. There seem to be two issues: Issue 1 is that the CC, CFLAGS, CXX, and CXXFLAGS settings are not reflected in the site.exp file. I had CC=gcc-4.2 CFLAGS="-m32 -Wl,-melf_i386" CXX=g++-4.2 CXXFLAGS=$CFLAGS

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 Mar 3, 2008, at 2:49 AM, Joachim Durchholz wrote: > Hi all, > > I found enough to explain the behaviour that I encountered. If I'm > correct, the bugs are just in the dejagnu-based test machinery, not in > LLVM itself. Yep, I believe that. I haven't been following the whole thread very closely, what specific tests are affected here? Before making any significant and

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.

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

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

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

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

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

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

For those of you running nightly tests: A new version of the NewNightlyTest.pl script needs to be propagated. This version supports checking LLVM out from Subversion and getting repository history data from Subversion. Unfortunately, it also requires the Date::Parse Perl module which is often not automatically installed. You will need to run cpan to get this installed. Please install this soon as

> 1. Improvements to the perl script which manage actual testing > (./util/NewNightlyTest.pl) > (a). compiling llvm-gcc > (b). allowing someone to use an existing tree versus checking out a > new one > 2. The improvements to the email that get sent to the llvm-testresults > (a). finding a point in time where some test failed > (b). comparing two

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

Hi, I downloaded and installed the front-end (llvm-gcc 4), and downloaded, configured, and built llvm-2.0 using -prefix=[myllvmPath] and -with-llvmgccdir=[llvm-gccPath] When I try to use sparc as target, llvm-gcc does not recognize it. I used -march=sparc and it gives two errors: "bad value (sparc) for -march= switch" "bad value (sparc) for -mtune= switch" I used

Am Mittwoch, den 27.02.2008, 14:31 -0800 schrieb Dale Johannesen: > On Feb 27, 2008, at 2:12 PM, Joachim Durchholz wrote: > > All error messages refer to one of the following four > > instructions: > > pushl %ebp > > pushl %esi > > popl %ebp > > popl %esi > > It's always the same error, "suffix or operands invalid for > >

I've made some modifications to the NewNightlyTest.pl script and I'm noticing many testers do not seem to update this script (judging from the data being submitted to our database). Please update the script manually, or modify you cron (or whatever you have controlling your tester) to automatically update the testing script before running the tests. Thanks, Tanya