similar to: [LLVMdev] Nightly Test Machines: Upgrade Needed

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

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

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, I thought I'd set up a nightly tester and ran across the following issues: 1) Checkout is done using https, which causes the following message: Error validating server certificate for 'https://llvm.org:443': - The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually! Certificate information: - Hostname: llvm.org -

All, At 0900 CDT tomorrow (1400 UTC) the Subversion migration will begin. At that time, CVS will be put in read-only mode while the conversion to Subversion is made. We expect the Subversion repository to be up and running 3 hours later at about 1200 CDT, 1000 PDT, or 1700 UTC. If you haven't got your subversion client yet, please do so now. If you host a nightly test, please get the latest

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.

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

Dear All, I need one or more volunteers to try out their nightly testers with the -usesvn option. We're not running on here at the University of Illinois regularly, so if someone could try one of theirs out before tomorrow 9:00 am CDT, I'd be very appreciative. Thanks. -- John T.

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

> 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

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

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

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

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 Fri, 2007-03-02 at 17:48 -0600, John Criswell wrote: > Dear All, > > I've just heard that there's been a recent discussion on the IRC channel > about moving the LLVM source repository from CVS to Subversion (SVN) and > that this migration may happen "soon." Yes, its been talked about for ages and its time to do it. We've debated the choice of repositories

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

Greetings, During the past week, there have been some requests for nightly tarballs to help making testing new Asterisk code easier. There was some debate as to whether they would be useful. The reason that they may not be useful is because you can get equivalent access to new code just by accessing the subversion repository directly. However, for one reason or another, some people would