Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 48118 invoked from network); 22 Feb 2011 01:01:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 Feb 2011 01:01:24 -0000 Received: (qmail 67185 invoked by uid 500); 22 Feb 2011 01:01:24 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 66940 invoked by uid 500); 22 Feb 2011 01:01:23 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 66932 invoked by uid 99); 22 Feb 2011 01:01:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Feb 2011 01:01:23 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 209.85.216.171 as permitted sender) Received: from [209.85.216.171] (HELO mail-qy0-f171.google.com) (209.85.216.171) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Feb 2011 01:01:16 +0000 Received: by qyj19 with SMTP id 19so1936365qyj.9 for ; Mon, 21 Feb 2011 17:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6s+dNgyt0xEWC/3D7YMXGUeguG8O3aCeqdS4V2BJml8=; b=WX+eGNlyiHU79QkmQJVb+lQ79vs0Yx63LypeiVwHwAkA93P3Yb5iFnW6LrxsyrwMYL qOCpeSxPeCgmJOAa0UJXh4Bdxk9xDPWHKzeCQhyxLilIACuUmBUpKNOwN83e9lpXDXBG X1coB+Cnk0WGRdjX7YXy0IMUP+g7UaNrrYYZk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=OFLxOJcT/4k00mUqOTYqnyvuQ5+MM1NkX4Jhexheg1H1MUJq3ll6V+vRNAlT5JKUsD iOyS8AERFxnu/+nMXsslZr95H8WHr2vA7jpNnDWswjDY7zNkrT1Dw48ya3Xycwx37DRl J+MuYnm3D2ySdza7HEgmT4VCXA34gVHaxLEh8= MIME-Version: 1.0 Received: by 10.229.251.139 with SMTP id ms11mr1477109qcb.198.1298336453730; Mon, 21 Feb 2011 17:00:53 -0800 (PST) Received: by 10.229.217.8 with HTTP; Mon, 21 Feb 2011 17:00:53 -0800 (PST) In-Reply-To: <4D62CA78.4010400@free.fr> References: <4D62BCF7.4070905@free.fr> <4D62CA78.4010400@free.fr> Date: Tue, 22 Feb 2011 01:00:53 +0000 Message-ID: Subject: Re: [MATH] 2.2 test failures when run with 2.1 test cases From: sebb To: Commons Developers List Cc: Luc Maisonobe Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On 21 February 2011 20:26, Luc Maisonobe wrote: > Le 21/02/2011 21:06, sebb a =E9crit : >> On 21 February 2011 19:28, Luc Maisonobe wrote: >>> Le 21/02/2011 18:03, sebb a =E9crit : >>>> I've updated the test-jar.xml Ant script [1] so it can now be used to >>>> run the test classes against a jar without needing to also compile >>>> against the jar: >>>> >>>> $ ant -f test-jar.xml [-lib junit-m.n..jar] test-only >>>> >>>> Running this against a checkout of [3] gives 40 classes with test >>>> errors or test failures. >>>> >>>> I'm sure some of these are due to fixes in the code which need >>>> corresponding test case changes. >>>> But are all the errors/failures expected? Further investigation is nee= ded. >>>> >>>> Compiling the 2.1 test cases against 2.2 results in 19 compilation err= ors. >>>> These seem to be OK, =A0as they relate to EventState and >>>> oacm.ode.DerivativeException >>> >>> No, this is a real problem. When reverting some changes, I forgot the >>> StepHandlerInterface which *is* a user level interface. >>> As of 2.1, it throws the checked exception DerivativeException. When we >>> first decided to change, the compatible way was to modify the base clas= s >>> of DerivativeException, so that users who already use this exception >>> will have no problem (we tested for both binary and source >>> compatibility, everything was OK binary-wise, and there was a >>> deprecation warning source-wise). >>> When we reverted this change, we forgot to change the interface back to >>> DerivativeException and let only the unchecked MathUserException in the >>> declaration of the interface. >>> >>> This means that users who implemented the interface *must* change their >>> implementation, so it is an incompatible change. >>> >>> Strangely enough, CLIRR did not detect it (see >>> , th= e >>> StepHandler interface appears nowhere)! >>> >>> I am going to cancel the vote for RC2 and change the interface back. >>> >>>> >>>> To re-run the tests: >>>> >>>> Checkout the 2.1 tag [3] >>>> Compile the code, e.g. >>>> mvn clean compiler:compile compiler:testCompile >>>> Copy the updated test-jar.xml file from [1] into top-level dir >>>> Copy commons-math-2.2.jar into top level dir. >>>> >>>> $ ant -f test-jar.xml [-lib junit-m.n..jar] test-only ! run tests >>>> against math 2.2 >>> >>> I was not able to run this. It seems the commons-math-2.2.jar is never >>> included in the classpath. I even tried to force it with a >>> part in the of the test-only target and it failed. >> >> Strange - are you using the latest test-jar.xml from branches/2_X? > > Yes, I checked out the 2.1 tag in a new directory and the 2.X branch in > a new directory next to it. I created the jar with "mvn package", then > copied both the jar from target subdirectory and the test-jar.xml in the > 2.X branch to the top level directory of the 2.1 tag. > >> And is the math 2.2 jar in the same dir? > > Yes, next to test-jar.xml , pom.xml and the like. It is named > commons-math-2.2.jar. > > I tried to run both the init and test-only target in the same run to see > the classpath, but it display the (huge) java.class.path, not the > classpath with the id build.classpath. Is there a way to print this one > too (I don't know well ant id/refid magic) ? There was a problem with the test-jar.xml - it was including jars from lower directories too. As it happened, I had a copy of junit under lib, so it worked for me. There was a further problem in that I'd set includeantruntime=3D"false" for the compile target, so JUnit could not be picked up from the Ant classpath. Sorry about that. If you try the current version, hopefully it will work now. > Luc > >> >>> I used ant 1.8.0 on a Linux box. >> >> I'm using Ant 1.8.0 on a WinXP. >> >>> Luc >>> >>>> >>>> $ ant -f test-jar.xml [-lib junit-m.n..jar] ! compile and run tests >>>> against math 2.2 >>>> >>>> The output has been uploaded to [2] >>>> >>>> [1] https://svn.apache.org/repos/asf/commons/proper/math/branches/MATH= _2_X/test-jar.xml >>>> [2] http://people.apache.org/~sebb/MATH2.2RC2 >>>> [3] http://svn.apache.org/repos/asf/commons/proper/math/tags/MATH_2_1 >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>>> For additional commands, e-mail: dev-help@commons.apache.org >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>> For additional commands, e-mail: dev-help@commons.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org