[
https://issues.apache.org/jira/browse/DERBY-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081064#comment-13081064
]
Myrna van Lunteren commented on DERBY-5373:
-------------------------------------------
This test fails on the Windows XP desktop machine on which suites.All is run
nightly (when there are changes) with weme 6.2 (as well as with ibm 1.5 and 1.6
jvm). I've tried to duplicate the behavior on my laptop, which is also running
Windows XP, with the same version of weme6.2, but it hasn't failed there. I've
tried this by running the test by itself, by running it in a modified tools
suite, by running the entire tools suite and running the entire suites.All.
As I can't reproduce this outside of the nightly process, I cannot version back
either, but the test did not fail on 7/27 (with the tree svn update-d up
revision 1151694), but did fail on 7/29 (with the tree svn update-d to revision
1152410).
The only change picked up on that date was revision 1152371.
I will continue investigating and will comment when I know something useful.
> 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
