Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <6657738.1196372563207.JavaMail.jira@brutus>
Date: Thu, 29 Nov 2007 13:42:43 -0800 (PST)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3222) 'CollationTest' fails with '
 expected:<1> but was:<0>' in testPolishCollation(CollationTest.java:402)
In-Reply-To: <29391345.1195728704402.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Mamta A. Satoor commented on DERBY-3222:
----------------------------------------

I am curious if this test is still failing on Solaris? The particular test case in CollationTest that is failing is as below
    rs = s.executeQuery("select vc from a where '' || CURRENT_DATE = vc");
    assertEquals(1,JDBC.assertDrainResults(rs));

But this test was added back in August, so I wonder why it's failing only now. The checkin info for the test case is as below
Date: Tue Aug 28 13:26:16 2007
New Revision: 570562


> 'CollationTest' fails with ' expected:<1> but was:<0>' in testPolishCollation(CollationTest.java:402)
> -----------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3222
>                 URL: https://issues.apache.org/jira/browse/DERBY-3222
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.3.1.5
>         Environment: OS: Solaris 10 8/07 s10x_u4wos_12b X86 64bits - SunOS 5.10 Generic_120012-14
> JVM: Sun Microsystems Inc. 1.6.0_01-b06
>            Reporter: Ole Solberg
>
> See http://dbtg.thresher.com/derby/test/10.3Branch/jvm1.6/testing/Limited/testSummary-597152.html : sol.
> There was 1 failure:
> 1) testPolishCollation(org.apache.derbyTesting.functionTests.tests.lang.CollationTest)junit.framework.AssertionFailedError: expected:<1> but was:<0>
> 	at org.apache.derbyTesting.functionTests.tests.lang.CollationTest.commonTestingForTerritoryBasedDB(CollationTest.java:1141)
> 	at org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testPolishCollation(CollationTest.java:402)
> 	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:88)
> 	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)

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