similar to: [LLVMdev] GSoC: Improving nightly tester

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

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 >

Thanks :-) One last thing. It seems like the patch has a lot of whitespace changes. Could you create the diff with the -b option? -bw On Mon, Jul 7, 2008 at 11:49 AM, Rajika Kumarasiri <rajikacc at gmail.com> wrote: > hi Bill, > Thanks for the comments. I'll update the patch according to that. > > -Rajika > > On Mon, Jul 7, 2008 at 11:56 PM, Bill Wendling

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

hi Bill, Thanks for the comments. I'll update the patch according to that. -Rajika On Mon, Jul 7, 2008 at 11:56 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Mon, Jul 7, 2008 at 11:10 AM, Rajika Kumarasiri <rajikacc at gmail.com> > wrote: > > hello everybody, > > > > I have added few improvements to my patch. Please review the new patch > >

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

On Mon, Jul 7, 2008 at 11:10 AM, Rajika Kumarasiri <rajikacc at gmail.com> wrote: > hello everybody, > > I have added few improvements to my patch. Please review the new patch > directly. > Thanks! > Hi Rajika, A few stylistic comments. I'll let others comment on the algorithm for now: if ($VERBOSE) { print "( time -p $SVNCMD/llvm/trunk llvm; cd

Another suggestion: a web service that would allow you to submit a test build and it would provide you feedback on deviations from known good for that target. I know a lot of people keep two trees around for this purpose, and I'd personally like to ditch the duplicate if I could. -- Chris On Mar 21, 2008, at 9:22 PM, Rajika Kumarasiri wrote: > Hello every body, > Thank you all

hello every body, This suppose to be the work done by me so far. 1. Set up a local replica of LLVM nightly tester. 2. Read and understood how nightlytester works together with nightly tester script, NewNightlyTester.pl 3. Added a patch to nightly tester script (NewNightlyTester.pl) adding the capabilities: checking out the llvm-gcc source, compiling llvm-gcc, and gather required information

On Mar 8, 2008, at 10:46 PM, Rajika Kumarasiri wrote: > Hello every body, > I am a Computer Science and Engineering final year undergraduate in > here [1]. > As you all aware of GSoC 2008 program is now on [2]. I would like to > participate in this on a project on LLVM. The reason why I selected > LLVM is I am really interested in compiler theory. > I took the one

Hello every body, With the ideas and suggestions that I got from you all I came up with the proposal for the project of improving the llvm-test testsuite. I am posting my proposal here, if you have any feedback(anything to be added or anything to be removed ) please let me know, so that I can improve the proposal before I upload it in Google web app. Thanks in advance.! Regarda, Rjika *Proposal

Hello every body, Thank you all for your great suggestions and feedbacks, I'd forward the detailed proposal within couple of days. And also if I need to clarify any thing I'll ask in the list. Thanks again. Regards, Rajika On Thu, Mar 20, 2008 at 10:35 PM, Duncan Sands <baldrick at free.fr> wrote: > While on the subject of the testsuite, some random thoughts: > > - show

Hello every body, I am a Computer Science and Engineering final year undergraduate in here [1]. As you all aware of GSoC 2008 program is now on [2]. I would like to participate in this on a project on LLVM. The reason why I selected LLVM is I am really interested in compiler theory. I took the one semester course on compiler theory and developed a lexical analyzer in C for a subset of Javascript

hello everybody, I would like to improve the llvm-test suite[1] as a part of GSoC 2008 program for LLVM. I have few concerns/problems regarding this, please give me your feedbacks and suggestions to come up with the proper proposal. *Goal:* Improve the llvm-test testsuite. *Idea:* Extend the llvm-test testsuite to include new programs and benchmarks[2]. Test programs should be more CPU intensive

> 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 everybody, I am very much happy to announce that my GSoC 2008 proposal[1] was accepted. Thank you very much for accepting my proposal. My mentor is Tanya Lattner. I would like to know how should I communicate with my mentor( using this dev-list, #llvm at Oftc.net or by any other means)? I started to work on my project(right now I am further looking into the nightly tester source[2] and the

Am Mittwoch, den 19.03.2008, 10:22 +0530 schrieb Rajika Kumarasiri: > 2. As described llvm testsuite program should be more CPU intensive > programs, is there is any reason for that and how a llvm test suite > program can make more CPU intensive, any points that should consider > to write a more CPU intensive test program for llvm? I guess that's just trying to get the most

> > 4. Running Fortran, Ada, C/C++/ObjC tests as well with test results emailed > > to the llvm-testresults. > > Are these different or new tests? Why wouldn't they just be a part of the > llvm-test module? Then you don't have to do any modifications to the > scripts. Probably means the gcc testsuite. Ciao, Duncan.

>>> 4. Running Fortran, Ada, C/C++/ObjC tests as well with test results emailed >>> to the llvm-testresults. >> >> Are these different or new tests? Why wouldn't they just be a part of the >> llvm-test module? Then you don't have to do any modifications to the >> scripts. > > Probably means the gcc testsuite. Well then this should be