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 "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2011/01/06 19:45:46 UTC

[jira] Resolved: (DERBY-4713) Subclasses of ScriptTestCase can not run correctly with the non-English default locale

     [ https://issues.apache.org/jira/browse/DERBY-4713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren resolved DERBY-4713.
---------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.8.0.0
    Issue & fix info:   (was: [Patch Available])

I've committed patch derby-4713-2 with revision 1055998.

With this patch, I did not see any unexpected test failures in a run of suites.All (sane build, classes - ibm 1.6 - I saw one intermittent server ping issue in testSetPortPriority and testPing failed for me).

Looking at the code of the patch, it seemed ike it would be an improvement.
Running suites.All with -Duser.language=zh_CN I still saw a lot of failures, including some of the scriptTestCase tests, but I'm assuming that it's a problem with that setup, as Yun Lee said tests passed for him with the patch where before they failed.


> Subclasses of ScriptTestCase can not run correctly with the non-English default locale
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-4713
>                 URL: https://issues.apache.org/jira/browse/DERBY-4713
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>            Reporter: Yun Lee
>            Assignee: Yun Lee
>             Fix For: 10.8.0.0
>
>         Attachments: bit.out, derby-4713-1.patch, derby-4713-1.stat, derby-4713-2.patch, derby-4713-2.stat, derby-4713.patch, derby-4713.stat
>
>
> If the default locale is not English, many subclasses of ScriptTestCase will fail. 
> For example, run NetIjTest (a subclass of ScriptTestcase)  in a Chinese OS, the test case will fail:
> D:\derby\test>java junit.textui.TestRunner org.apache.derbyTesting.functionTests
> .tests.derbynet.NetIjTest
> .F
> Time: 5.422
> There was 1 failure:
> 1) testclientij(org.apache.derbyTesting.functionTests.tests.derbynet.NetIjTest)j
> unit.framework.ComparisonFailure: Output at line 34 expected:<[ERROR 42X05: Tabl
> e/View 'APP.NOTTHERE' does not exist.]> but was:<[?? 42X05??????APP.NOTTHERE????
> ?]>
>         at org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon
> (CanonTestCase.java:106)
>         at org.apache.derbyTesting.functionTests.util.ScriptTestCase.runTest(Scr
> iptTestCase.java:198)
>         at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:
> 109)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
>         at junit.extensions.TestSetup.run(TestSetup.java:27)
>         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:23)
>         at junit.extensions.TestSetup.run(TestSetup.java:27)
>         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:23)
>         at junit.extensions.TestSetup.run(TestSetup.java:27)
>         at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>         at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
>         at junit.extensions.TestSetup.run(TestSetup.java:27)
> FAILURES!!!
> Tests run: 1, Failures: 1, Errors: 0 
> While, it succeed running with a English-language lcoale.
> D:\derby\test>java -Duser.language=en junit.textui.TestRunner org.apache.derbyTe
> sting.functionTests.tests.derbynet.NetIjTest
> .
> Time: 6.187
> OK (1 test)

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