Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 80404 invoked from network); 10 Apr 2010 18:39:53 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Apr 2010 18:39:53 -0000 Received: (qmail 65548 invoked by uid 500); 10 Apr 2010 18:39:52 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 65499 invoked by uid 500); 10 Apr 2010 18:39:52 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 65492 invoked by uid 99); 10 Apr 2010 18:39:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Apr 2010 18:39:52 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-inf-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 10 Apr 2010 18:39:42 +0000 Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe1.eu.sun.com [192.18.6.7] (may be forged)) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id o3AIdLQs010789 for ; Sat, 10 Apr 2010 18:39:21 GMT MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_Z5PxrwzKWrM5moFUM47WPQ)" Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) id <0L0O00F00BJ42E00@fe-emea-10.sun.com> for derby-dev@db.apache.org; Sat, 10 Apr 2010 19:39:05 +0100 (BST) Received: from [192.168.0.199] ([unknown] [84.215.174.92]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.04 64bit (built Jul 2 2009)) with ESMTPSA id <0L0O00EOIBT5UG70@fe-emea-10.sun.com> for derby-dev@db.apache.org; Sat, 10 Apr 2010 19:39:05 +0100 (BST) Date: Sat, 10 Apr 2010 20:39:05 +0200 From: Kristian Waagan Subject: Re: Fw: Juni Tests In-reply-to: Sender: Kristian.Waagan@Sun.COM To: derby-dev@db.apache.org Message-id: <4BC0C5C9.7010409@Sun.COM> Organization: Sun Microsystems Inc. References: <901820.44561.qm@web29116.mail.ird.yahoo.com> <4BC08E73.4010809@gmail.com> <4BC09FC0.6010307@gmail.com> <227284.45994.qm@web29110.mail.ird.yahoo.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nb-NO; rv:1.9.1.4pre) Gecko/20090915 Lightning/1.0b1 Thunderbird/3.0b4 X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --Boundary_(ID_Z5PxrwzKWrM5moFUM47WPQ) Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On10.04.2010 18:37, Nirmal Fernando wrote: > Thanks Tiago !! > > Ya, I ran the command that Bryan had posted few mails ago. It included > those maximizing memory allocation. > > By the way, at what times we need to run suites.All? Is it only when > we create a patch? I run suites.All with as good as every patch I commit. The exceptions are JavaDoc changes only, or other trivial changes. Sometimes I have committed what I believed was trivial changes, and then one or more tests failed in the nightly tests run by members of the community... Sometimes tests fail on some platforms only, so you may see failures in the nightlies even if the tests passed on your own machine. Running the regression tests is a good way to root out problems with patches early on. If you're working on a patch and you know specific tests are failing (maybe after running suites.All for the first time), it is better to keep running the specific test(s) until the errors have been corrected, otherwise your iterations will take a very long time. When you feel the code is ready, you can start the full suite again. For JUnit, run org.apache.derbyTesting.functionTests.tests.[directory]._Suite to run all tests within the specified directory (a Derby convention). As I mentioned above, some people run suites.All every day and post the results to derby-dev. For instance, see Ole's results at http://dbtg.foundry.sun.com/derby/test/ . As a developer, unless you have a special interest in testing, running the regression tests when you test patches should be sufficient. Sometimes running the tests with a clean code base is helpful to verify that the tests are running fine on your machine. Regards, -- Kristian > > > Thanks!!! > > On Sat, Apr 10, 2010 at 9:56 PM, Tiago Espinha > > wrote: > > Hello Nirmal, > > I'm glad that you finally got it running. The how long tests take > to run depends a lot on the machine you're running them on and > even on the operating system. There are a few tests that if I > recall correctly take ages on Windows but are much faster on *nix > systems. > > Since you're running them on Windows and with an average dual core > computer, you're looking at at least 3 or 4 hours for the whole > suites.All. > > Also be wary that if this: > > java junit.testui.TestRunner > org.apache.derbyTesting.functionTests.suites.All > > is the way you're running your suites.All, your run will most > certainly fail. There are some tests in suites. All that require a > great deal of memory and it's easy to exhaust the 128Mb(?) limit > imposed by default on each JVM. > > Here's what I use: > > java -Xms128m -Xmx1024m -XX:MaxPermSize=512m > junit.textui.TestRunner > org.apache.derbyTesting.functionTests.suites.All > > I start with 128Mb of memory allocated, allow it to expand to 1Gb > and that last argument I believe has to do with the size of the > heap, as it does run out for some of the tests as well. > > Hope it helps, > Tiago > > ------------------------------------------------------------------------ > *From:* Nirmal Fernando > > *To:* derby-dev@db.apache.org > *Sent:* Sat, 10 April, 2010 17:17:33 > > *Subject:* Re: Fw: Juni Tests > > Hi All, > > I think I found the reason, it's just that I'm using Windows Vista > not Unix. > > So in Windows my CLASSPATH variable's value should be following: > > %jardir%\derby.jar;%jardir%\derbytools.jar;%jardir%\derbyrun.jar;%jardir%\derbynet.jar;%jardir%\derbyclient.jar;%jardir%\derbyTesting.jar;%tstjardir%\jakarta-oro-2.0.8.jar;%tstjardir%\junit.jar;%jardir%\derbyLocale_cs.jar;%jardir%\derbyLocale_de_DE.jar;%jardir%\derbyLocale_es.jar;%jardir%\derbyLocale_fr.jar;%jardir%\derbyLocale_hu.jar;%jardir%\derbyLocale_it.jar;%jardir%\derbyLocale_ja_JP.jar;%jardir%\derbyLocale_ko_KR.jar;%jardir%\derbyLocale_pl.jar;%jardir%\derbyLocale_pt_BR.jar;%jardir%\derbyLocale_ru.jar;%jardir%\derbyLocale_zh_CN.jar;%jardir%\derbyLocale_zh_TW.jar > > Note: *In Windows you have to use %aa% instead of $aa and ";" > instead of ":".* > * > * > * > * > * > Now I'm running Suites.All !! :) Usually how long will take to last? > > Thanks for all of you for your replies !!! > > > * > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Department of Computer Science & Engineering, > Faculty of Engineering, > University of Moratuwa, > Sri Lanka. > > > > > -- > Best Regards, > Nirmal > > C.S.Nirmal J. Fernando > Department of Computer Science & Engineering, > Faculty of Engineering, > University of Moratuwa, > Sri Lanka. --Boundary_(ID_Z5PxrwzKWrM5moFUM47WPQ) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT On10.04.2010 18:37, Nirmal Fernando wrote:
Thanks Tiago !!

Ya, I ran the command that Bryan had posted few mails ago. It included those maximizing memory allocation. 

By the way, at what times we need to run suites.All? Is it only when we create a patch?

I run suites.All with as good as every patch I commit.
The exceptions are JavaDoc changes only, or other trivial changes. Sometimes I have committed what I believed was trivial changes, and then one or more tests failed in the nightly tests run by members of the community... Sometimes tests fail on some platforms only, so you may see failures in the nightlies even if the tests passed on your own machine.
Running the regression tests is a good way to root out problems with patches early on.

If you're working on a patch and you know specific tests are failing (maybe after running suites.All for the first time), it is better to keep running the specific test(s) until the errors have been corrected, otherwise your iterations will take a very long time. When you feel the code is ready, you can start the full suite again.
For JUnit, run org.apache.derbyTesting.functionTests.tests.[directory]._Suite to run all tests within the specified directory (a Derby convention).

As I mentioned above, some people run suites.All every day and post the results to derby-dev. For instance, see Ole's results at http://dbtg.foundry.sun.com/derby/test/ .
As a developer, unless you have a special interest in testing, running the regression tests when you test patches should be sufficient.
Sometimes running the tests with a clean code base is helpful to verify that the tests are running fine on your machine.


Regards,
--
Kristian



Thanks!!!

On Sat, Apr 10, 2010 at 9:56 PM, Tiago Espinha <tiago.derby@yahoo.co.uk> wrote:
Hello Nirmal,

I'm glad that you finally got it running. The how long tests take to run depends a lot on the machine you're running them on and even on the operating system. There are a few tests that if I recall correctly take ages on Windows but are much faster on *nix systems.

Since you're running them on Windows and with an average dual core computer, you're looking at at least 3 or 4 hours for the whole suites.All.

Also be wary that if this:

java junit.testui.TestRunner org.apache.derbyTesting.functionTests.suites.All

is the way you're running your suites.All, your run will most certainly fail. There are some tests in suites. All that require a great deal of memory and it's easy to exhaust the 128Mb(?) limit imposed by default on each JVM.

Here's what I use:

java -Xms128m -Xmx1024m -XX:MaxPermSize=512m junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All

I start with 128Mb of memory allocated, allow it to expand to 1Gb and that last argument I believe has to do with the size of the heap, as it does run out for some of the tests as well.

Hope it helps,
Tiago

From: Nirmal Fernando <nirmal070125@gmail.com>
To: derby-dev@db.apache.org
Sent: Sat, 10 April, 2010 17:17:33

Subject: Re: Fw: Juni Tests

Hi All,

I think I found the reason, it's just that I'm using Windows Vista not Unix. 

So in Windows my CLASSPATH variable's value should be following:

%jardir%\derby.jar;%jardir%\derbytools.jar;%jardir%\derbyrun.jar;%jardir%\derbynet.jar;%jardir%\derbyclient.jar;%jardir%\derbyTesting.jar;%tstjardir%\jakarta-oro-2.0.8.jar;%tstjardir%\junit.jar;%jardir%\derbyLocale_cs.jar;%jardir%\derbyLocale_de_DE.jar;%jardir%\derbyLocale_es.jar;%jardir%\derbyLocale_fr.jar;%jardir%\derbyLocale_hu.jar;%jardir%\derbyLocale_it.jar;%jardir%\derbyLocale_ja_JP.jar;%jardir%\derbyLocale_ko_KR.jar;%jardir%\derbyLocale_pl.jar;%jardir%\derbyLocale_pt_BR.jar;%jardir%\derbyLocale_ru.jar;%jardir%\derbyLocale_zh_CN.jar;%jardir%\derbyLocale_zh_TW.jar

Note: In Windows you have to use %aa% instead of $aa and ";" instead of ":".


Now I'm running Suites.All !! :) Usually how long will take to last? 

Thanks for all of you for your replies !!!


--
Best Regards,
Nirmal

C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.




--
Best Regards,
Nirmal

C.S.Nirmal J. Fernando
Department of Computer Science & Engineering,
Faculty of Engineering,
University of Moratuwa,
Sri Lanka.

--Boundary_(ID_Z5PxrwzKWrM5moFUM47WPQ)--