You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bryan Pendleton (JIRA)" <ji...@apache.org> on 2011/08/05 02:54:27 UTC
[jira] [Commented] (DERBY-5373) test ImportExportIJ fails with weme
6.2; junit.framework.ComparisonFailure: Output at line 1 expected: -->
but was:
[ https://issues.apache.org/jira/browse/DERBY-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079711#comment-13079711 ]
Bryan Pendleton commented on DERBY-5373:
----------------------------------------
Possibly the same fix will work here as was made for DERBY-5346?
> test ImportExportIJ fails with weme 6.2; junit.framework.ComparisonFailure: Output at line 1 expected:<ij> --> but was:<ERROR XJ004: Database '' not found.>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5373
> URL: https://issues.apache.org/jira/browse/DERBY-5373
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.9.0.0
> Environment: windows XP, with weme 6.2 (CDC/Foundation profile)
> Reporter: Myrna van Lunteren
>
> The test importExportIJ started failing on 7/29/2011 in the nightly test with weme 6.2 (IBM's CDC/Foundation profile implementation) - this was with trunk sync-ed up to revision 1152410.
> Likely this is related to the change of revision 1151691 for DERBY-5342 (make ScriptTestCase support ij properties)
> This is the stack trace:
> 1) importExportIJ(org.apache.derbyTesting.functionTests.tests.tools.ImportExportIJTest)junit.framework.ComparisonFailure: Output at line 1 expected:<ij> --> but was:<ERROR XJ004: Database '' not found.>
> at junit.framework.AssertionFailedError.<init>(AssertionFailedError.java:11)
> at junit.framework.ComparisonFailure.<init>(ComparisonFailure.java:19)
> at org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:109)
> at org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(ScriptTestCase.java:204)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:112)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira