similar to: [LLVMdev] Nightly Tester Volunteers

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

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

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

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

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

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

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

All, 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. Directions to set up a tester are here: http://llvm.org/docs/TestingGuide.html#nightly These directions could be improved of course. If you have any questions, I will be happy to assist you in

hello everybody, I have added few improvements to my patch. Please review the new patch directly. Thanks! -Rajika On Sun, Jul 6, 2008 at 9:17 PM, Rajika Kumarasiri <rajikacc at gmail.com> wrote: > 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 >

On Feb 16, 2008, at 7:06 AM, Apache wrote: > New Test Failures: > test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU] This test doesn't work with gcc-4.0, which caused it to fail on a number of testers overnight. I can fix that in 4.0, but as I understand it we're going to drop support for it next release, so how about now?

>> llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind >> that you need to keep llvm-gcc in sync with llvm (same revision number). > > This basically means llvm-gcc needs to be rebuild every time llvm > is built and the test run. Shouldn't this be part of > NewNightlyTest.pl then? Yes. Patches accepted ;) There is a GSOC student that is supposed

> 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

On Sat, 30 Dec 2006, Reid Spencer wrote: > You all just need remove "stacker_rt.ll". the stacker_rt.ll is a > generated file, not source. The Makefile should have a dependency on > llvm-gcc for it, but doesn't. Just remove stacker_rt.ll and the problem > will go away. This presumably doesn't impact the testers, as they start from a clean build every night. The

You all just need remove "stacker_rt.ll". the stacker_rt.ll is a generated file, not source. The Makefile should have a dependency on llvm-gcc for it, but doesn't. Just remove stacker_rt.ll and the problem will go away. Reid. On Sat, 2006-12-30 at 08:37 -0500, Nick Lewycky wrote: > Jim Laskey wrote: > > llvm[4]: Compiling stacker_rt.ll to stacker_rt.bc for Release build

But I am using llvm-gcc-4.2. Any idea why it's failing? Evan On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > On Feb 16, 2008, at 7:06 AM, Apache wrote: >> New Test Failures: >> test/C++Frontend/2008-02-13-sret.cpp [DEJAGNU] > > This test doesn't work with gcc-4.0, which caused it to fail on a > number of testers overnight. I can fix that in 4.0, but as I

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

On Feb 16, 2008, at 11:32 AM, Evan Cheng wrote: > But I am using llvm-gcc-4.2. Any idea why it's failing? > > Evan All the failing testers are using gcc-4.0 according to the web pages they point at. > On Feb 16, 2008, at 11:24 AM, Dale Johannesen wrote: > >> On Feb 16, 2008, at 7:06 AM, Apache wrote: >>> New Test Failures: >>>

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