similar to: [LLVMdev] NewNightlyTest.pl - Please update

On Mar 8, 2008, at 2:45 PM, Joachim Durchholz wrote: > > Am Samstag, den 08.03.2008, 14:02 -0800 schrieb Tanya Lattner: >> - ability to check out llvm-gcc or update llvm-gcc and build it >> before >> running tests. In addition to using a prebuilt binary. > > Does it need a prebuilt binary? > I have been suspecting so since it has been failing with BUILD ERROR

On Thu, Jun 5, 2008 at 2:50 PM, Tanya M. Lattner <tonic at nondot.org> wrote: > > >> 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.

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

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

Am Samstag, den 08.03.2008, 14:02 -0800 schrieb Tanya Lattner: > - ability to check out llvm-gcc or update llvm-gcc and build it before > running tests. In addition to using a prebuilt binary. Does it need a prebuilt binary? I have been suspecting so since it has been failing with BUILD ERROR for me. I just haven't found the time to verify that yet. I have yet to try building

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

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

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

> 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

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

On Thu, 2007-04-05 at 14:07 -0700, Chris Lattner wrote: > On Thu, 5 Apr 2007, Reid Spencer wrote: > > This is a reminder that the script will change so that tonight's nightly > > test will use the hybrid svn/cvs version. This requires the Date::Parse > > perl module. If you haven't installed it yet, please do so before the > > next run of your nightly test. >

On Mar 8, 2008, at 10:57 AM, Joachim Durchholz wrote: > Hi all, > > when looking at NewNightlyTester.pl, I see it has several distinct > phases: > > 1. Get a current tree > 2. ./configure > 3. Build > 4. Run a selection of tests > 7. Send test results to web site > 8. Clean up > > Wouldn't it make sense to allow each phase to be activated >

On Thu, 5 Apr 2007, Reid Spencer wrote: > This is a reminder that the script will change so that tonight's nightly > test will use the hybrid svn/cvs version. This requires the Date::Parse > perl module. If you haven't installed it yet, please do so before the > next run of your nightly test. Hi Reid, We didn't have a chance to talk about this much when this came up, but

On Thu, 5 Apr 2007, Reid Spencer wrote: >> this is another dependency people have to satisfy to be able to run the >> nightly tester. Is there any way to avoid this? > > Only two things I can think of: > > 1. Forgo having "what changed" information in the nightly test > 2. Ask Anton to write the date parsing without using Date::Parse and do > the parsing

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

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

All, I've updated the NewNightlyTest.pl script again to fix a bug. If you're running this script, please make a note of the following: * There was a bug that only allowed the script to work with SVN if the -verbose option was also given (yeah, go figure). That's been fixed now. * The script now defaults to checkout from subversion so there is no

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.

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

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