db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1726) Make i18n/LocalizedDisplay.sql and i18n/LocalizedConnectionAttribute.sql behave equally on different platforms
Date Wed, 06 Aug 2008 19:12:44 GMT

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

Myrna van Lunteren updated DERBY-1726:
--------------------------------------

    Attachment: DERBY-1726_8.diff

Attaching one more cut at this patch, _8.diff. This differs from the previous one (_7.diff)
in 2 ways:
1. exits the tests (and i18n._Suite) if user.language is not en. 
   The master files are generated in an english locale, and have been morphed by the output.encoding.
Running them on a system with another locale (I tried on a japanese windows system (chcp 932,
user.language=ja) and it failed as I suspected. (When I started the tests on that system with
-Duser.language=en it was ok, but I don't think we should or can set user.language inside
a java program).

2. exits the tests (and i18n._Suite) if the jvm is JSR169.
   The LocalizedConnectionAttribute script contains a connect as which uses a protocol and
would cause a java.sql.Driver not found error. LocalizedDisplay script contains a decimal
datatype which does not get localized (see DERBY-470) and causes a diff.

I intend to commit this patch shortly.
I've ran varieties of combinations of tests (from suites.All to single tests) on various systems
(win (en and ja), linux, iseries) and with various jvms (sun, ibm (incl. weme6.1)).

> Make i18n/LocalizedDisplay.sql and i18n/LocalizedConnectionAttribute.sql behave equally
on different platforms
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1726
>                 URL: https://issues.apache.org/jira/browse/DERBY-1726
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.1.6
>            Reporter: Knut Anders Hatlen
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>         Attachments: DERBY-1726_1.diff, DERBY-1726_2.diff, DERBY-1726_3.diff, DERBY-1726_3.stat,
DERBY-1726_4.diff, DERBY-1726_5.diff, DERBY-1726_6.diff, DERBY-1726_7.diff, DERBY-1726_7.stat,
DERBY-1726_8.diff, props.java
>
>
> Myrna van Lunteren commented on DERBY-244:
> The one remark I have is that I still cannot get the LocalizedDisplay.sql and LocalizedConnectionAttribute.sql
test from the i18n directory to behave the same under windows and Linux (with sun jdk 1.4.2.).
> For windows, I had to update the masters for these tests, but running them on Linux still
failed for me.
> With jdk131, ibm131 and ibm142 the LocalizedDisplay.sql test hung, and LocalizedConnectionAttribute
exits with a MalformedInputException.
> It would be nice if we could figure out a way to add these tests to the suites...
> --- stack of LocalizedConnectionAttribute on Linux ---
> Exception in thread "main" sun.io.MalformedInputException
>         at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java(Compiled Code))
>         at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
>         at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
>         at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
>         at java.io.InputStreamReader.read(InputStreamReader.java:208)
>         at java.io.BufferedReader.fill(BufferedReader.java:153)
>         at java.io.BufferedReader.readLine(BufferedReader.java:316)
>         at java.io.BufferedReader.readLine(BufferedReader.java:379)
>         at org.apache.derbyTesting.functionTests.harness.RunTest.setDirectories(RunTest.java:729)
>         at org.apache.derbyTesting.functionTests.harness.RunTest.main(RunTest.java:262)
> ---------------------------------------------------------------------------- 

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