similar to: [LLVMdev] NewNightlyTest.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

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

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

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

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

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, 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 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, Chris. > I agree. Is the date in a fixed format? wouldn't a simple regex do the > trick? It seems it doesn't have fixed format. At least it: 1. Outputs local time. 2. Date string contains national symbols We should parse date by hands and filter revisions, which took place during prev. day. So, in general we need 2 routines: 1. Parse date into some internal format. 2.

Adam, > Do you have some examples of the string to parse? Surely (I don't know, what's the output with different locales): Moved for versioning. ------------------------------------------------------------------------ r33 | jlaskey | 2006-08-01 00:59:18 +0400 (Втр, 01 Авг 2006) | 1 line Moved for versioning. ------------------------------------------------------------------------ r32

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

If you run a nightly test .. 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. If you don't have time to do this, please make a copy of the existing script and use that copy to run your

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.

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

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 >

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

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

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

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 >

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 individually? Or possibly a subset of phases, something along the lines of -from-phase=test -to-phase=report With that, I could