db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <j...@apache.org>
Subject [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...>
Date Wed, 26 Sep 2007 23:56:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530602
] 

A B commented on DERBY-3054:
----------------------------

Looks like this was *not* just a one-time failure.  I've seen this test fail with weme6.1
twice in the last week.  The lines of input in question are:

  ERROR X0Y23: Operation 'DROP SYNONYM' cannot be performed on
    object 'MYSYN' because VIEW 'V1' is dependent on that object.

  ERROR X0Y23: Operation 'DROP SYNONYM' cannot be performed on
    object 'MYSYN' because VIEW 'V2' is dependent on that object.

Looks like the order of the two error messages is perhaps not guaranteed, so the "V2" message
is sometimes printed before the "V1" message...is that a possibility?  And if so, what's the
best to way avoid this failure?

> 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
>
> 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.


Mime
View raw message