db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jayaram Subramanian <rsjay1...@gmail.com>
Subject Re: (DERBY-5010) [patch] bad equivalence check
Date Tue, 19 Apr 2011 03:06:53 GMT
Hi,
When i tried doing something like

java -Dderby.tests.trace=true junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.lang._Suite >
runoutputApril17.out 2>&1

I get
.F
Time: 0.004
There was 1 failure:
1) warning(junit.framework.TestSuite$1)junit.framework.AssertionFailedError:
No tests found in
org.apache.derbyTesting.functionTests.util.ScriptTestCase

FAILURES!!!
Tests run: 1,  Failures: 1,  Errors: 0

Am i missing something here ?

With Regards
Jayaram


On Sun, Apr 17, 2011 at 12:47 PM, Knut Anders Hatlen
<knut.hatlen@oracle.com> wrote:
> Jayaram Subramanian <rsjay1976@gmail.com> writes:
>
>> Thanks all,
>> When i see the logs i am seeing that the test which calls isequivalent method is
>>
>> org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(ScriptTestCase.java:188)
>>
>> The line 188 in scripttestcase has
>> org.apache.derby.tools.ij.runScript(
>>                               conn,
>>                               sqlIn,
>>                               inputEncoding,
>>                 getOutputStream(),
>>                               outputEnc,
>>                 useSystemProperties);
>>
>>
>> i will try to direct the sqlin to the logs and try to find out the sql
>> which gets executed
>
> I think running with -Dderby.tests.trace=true should make ScriptTestCase
> print the name of the script it's running. Then perhaps you could run
> that script manually in ij and see which statement it executed right
> before the stack was printed.
>
> --
> Knut Anders
>

Mime
View raw message