db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-323) Locale problem in test of derby
Date Fri, 14 Jul 2006 07:06:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-323?page=all ]

Knut Anders Hatlen updated DERBY-323:
-------------------------------------

    Attachment: derby-323-v1.diff
                derby-323-v1.stat

Attached a patch (derby-323-v1.diff) which makes derbyall run
cleanlier with non-US locales. The patch does:

  1) Rewrite tools/derbyrunjartest.java to use jvm.getCommandLine() to
     get the command line to start the test with.

  2) Move the setting of user.language and user.country from RunTest
     and NetServer to jvm.getCommandLine(). This way, all of the java
     processes that are forked from the test harness or from a test
     get the same locale.

  3) Add Locale.setDefault(Locale.US) to RunTest.main(). This fixes
     the issue with the nist tests.

With this patch, derbyall runs cleanly with most locales, for instance
pt_BR, de_DE and ja_JP.UTF-8. However, three tests in i18nTest fail
with some variants of Japanese locale. ja_JP.ujis and ja_JP.SJIS have
these three failures. ja_JP.eucJP has these failures on some
platforms. I would assume other locales with non-Unicode/non-Latin
character sets also could see these failures.

The failing tests are:

i18n/urlLocale.sql
i18n/messageLocale.sql
i18n/iepnegativetests_ES.sql

All the failures are caused by non-ascii characters that are printed
as '?' because they don't exist in the default character set for the
locale. I believe this could be fixed by a combination of running the
i18n tests with -Dfile.encoding=something and specifying encoding to
streams/readers in RunTest.

> Locale problem in test of derby
> -------------------------------
>
>          Key: DERBY-323
>          URL: http://issues.apache.org/jira/browse/DERBY-323
>      Project: Derby
>         Type: Bug

>   Components: Test
>  Environment: Japanese localed Windows using cygwiin
>     Reporter: Tomohito Nakayama
>  Attachments: derby-323-v1.diff, derby-323-v1.stat
>
> Many of derbyall fails at Japanese localed Windows when environment corresponding derbyLocale_JP.jar
exists in CLASSPATH.
> Almost all of derby_all was failed because all result message was generated in 
> Japanese , and that was different from master file.
> I tried next configuration ...
> conf_0:Exclude derbyLocale_jp.jar
> conf_1:Add option "-Duser.language=en -Duser.country=US"
> conf_2:Add option "-Djvmflags=-Duser.language=en -Duser.country=US"
> conf_3:Defiine environment variable _JAVA_OPTIONS=:-Duser.language=en -Duser.locale=us
> conf_4:Defiine environment variable LC_CTYPE:en_US
> conf_0 works well on derbyall suite but some of derbynetclientmats/derbynetmats in derbyall
suite was failed. Network module seems to have localed message in other resource.
> conf_1 works on derbynetclientsmats suite, but same configuration for derbyall suite
does not work at all.
> conf_2 does not work on derbynetclientsmats suite.
> conf_3 seems to work for locale problem but  "Picked up _JAVA_OPTIONS:" message cause
error in test.
> conf_4 does not works ...
> Now conf_0 seems to be reasonable method now.
> I think conf_3 may be reasonable direction to modify test suite. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message