db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mamta Satoor <msat...@gmail.com>
Subject Re: Failure in test_13_5494
Date Thu, 19 Apr 2012 22:45:20 GMT
Thanks everyone. Kathey helped track it down to an outdated version of
junit. Using the new junit has fixed the problem.

On Thu, Apr 19, 2012 at 2:42 PM, Knut Anders Hatlen
<knut.hatlen@oracle.com> wrote:
> Mamta Satoor <msatoor@gmail.com> writes:
>
>> Hi Rick,
>>
>> Thanks for taking the time to respond to my email. I am including
>> partial output from the debug run of the single test and this is what
>> the output looked like towards the end. Thanks.
>>
>> DEBUG: Preparing statement:
>>         select currentvalue from sys.syssequences seq, sys.sysschemas
>> s where s.schemaname = ? and seq.sequencename = ? and s.schemaid =
>> seq.schemaid
>> .DEBUG: execute java command:
>> DEBUG: command[0]C:\Program Files (x86)\IBM\Java60\jre\bin\java
>> DEBUG: command[1]-classpath
>> DEBUG: command[2]c:/p4clients/svnmain/client6/trunk/classes;c:/p4clients/svnmain/client6/trunk/tools/java/junit.jar;c:/p4clients/svnmain/client6/trunk/tools/java/jakarta-oro-2.0.8.jar
>> DEBUG: command[3]-Dderby.tests.defaultDatabaseName=DB_5494
>> DEBUG: command[4]junit.textui.TestRunner
>> DEBUG: command[5]-m
>
> Which version is your junit.jar? The -m option was introduced in JUnit
> 3.8.2. If you have an older version, just remove
> trunk/tools/java/junit.jar and run ant, and then the right version
> should be downloaded automatically.
>
> --
> Knut Anders

Mime
View raw message