db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-3027) CollationTest fails with "Unexpected row count: expected:<0> but was:<1>" when Xalan 2.7 jars are in classpath
Date Mon, 27 Aug 2007 06:15:30 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor reassigned DERBY-3027:
--------------------------------------

    Assignee: Mamta A. Satoor

> CollationTest fails with "Unexpected row count: expected:<0> but was:<1>"
when Xalan 2.7 jars are in classpath
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3027
>                 URL: https://issues.apache.org/jira/browse/DERBY-3027
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure, Test
>    Affects Versions: 10.4.0.0
>         Environment: Solaris 10, Sun Java SE 5.0, Sun Java SE 6, Xalan 2.7.0, Derby trunk
#569146
>            Reporter: Knut Anders Hatlen
>            Assignee: Mamta A. Satoor
>
> When I have the Xalan jars in the classpath, testEnglishCollation(), testNorwayCollation()
and testPolishCollation() fail with this stack trace:
> 1) testEnglishCollation(org.apache.derbyTesting.functionTests.tests.lang.CollationTest)junit.framework.AssertionFailedError:
Unexpected row count: expected:<0> but was:<1>
> 	at org.apache.derbyTesting.junit.JDBC.assertDrainResults(JDBC.java:540)
> 	at org.apache.derbyTesting.junit.JDBC.assertEmpty(JDBC.java:468)
> 	at org.apache.derbyTesting.functionTests.tests.lang.CollationTest.checkLangBasedQuery(CollationTest.java:1129)
> 	at org.apache.derbyTesting.functionTests.tests.lang.CollationTest.commonTestingForTerritoryBasedDB(CollationTest.java:1056)
> 	at org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testEnglishCollation(CollationTest.java:512)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> 	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)
> If I remove the Xalan jars from the classpath, the test runs cleanly.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message