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 "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2007/10/23 18:54:51 UTC
[jira] Commented: (DERBY-3054) lang/synonym.sql fails with weme 6.1
with junit.framework.ComparisonFailure: Output at line 383
expected:<...1...> but was:<...2...>
[ https://issues.apache.org/jira/browse/DERBY-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537071 ]
Mamta A. Satoor commented on DERBY-3054:
----------------------------------------
I have fixed this in main with revision 587553. Commit comments are as follows
DERBY-3054
The non-junit test, synonym.sql, tests the synonym dependency. The particular test case 2 views dependent on it.
Depending on the jvm being used, the 2 exceptions(with same sql state but different object dependency in the sql
message text) thrown for dependency might be in different order and that causes test failure. In order to fix this,
I have carved out that test from synonym.sql into a new junit test and since in junit test, we can simply assert
the sql state, the order of 2 exceptions does not matter. I will migrate this fix into Derby 10.3 soon.
> lang/synonym.sql fails with weme 6.1 with junit.framework.ComparisonFailure: Output at line 383 expected:<...1...> but was:<...2...>
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-3054
> URL: https://issues.apache.org/jira/browse/DERBY-3054
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Mamta A. Satoor
>
> synonym(org.apache.derbyTesting.functionTests.tests.lang.LangScripts) failed:
> junit.framework.ComparisonFailure: Output at line 383 expected:<...1...> but was:<...2...>
> at junit.framework.Assert.assertEquals(Assert.java:81)
> at org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:100)
> at org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(ScriptTestCase.java:124)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:95)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.extensions.TestSetup.run(TestSetup.java:23)
> at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at TimeRunner.main(TimeRunner.java:31)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.