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] Commented: (DERBY-1726) Make i18n/LocalizedDisplay.sql and i18n/LocalizedConnectionAttribute.sql behave equally on different platforms
Date Tue, 10 Jun 2008 17:51:45 GMT

    [ https://issues.apache.org/jira/browse/DERBY-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603948#action_12603948

Myrna van Lunteren commented on DERBY-1726:

I was poking at this, thinking maybe these 2 .sql files could be funneled through junit, with
some checking for desired environment settings (if undesired, return empty suite) and some

But I encountered some issues:
1. I am aware of 2 ways of running a .sql script through ij from junit; 
    a. use ij.runScript
    b. extend util.IjTestCase (uses ij.main("-fr", "fileName");
    (See also DERBY-3088)
    There are some differences related to this, specifically, 
     + the output with ij.runScript does not include the ij a version number 
       This is + because otherwise we'd have to keep updating the master.
     - the output with ij.runScript does not include messages re rows  inserted/updated/deleted
       In these tests this is relevant, because we won't have a check to see whether those
messages still get translated. 

2. If one runs the test LocalizedConnectionAttribute.sql with RunTest, currently the connect
... as ... fails. That's also how the master file is checked in.
   a. I could duplicate this behavior when manually running ij without -Dderby.ui.locale=de_DE.
The test, however, has that setting in LocalizedConnectionAttribute_app.properties, so, I'm
wondering if properties are honored properly with the old harness...
    b. this connection has a create=true, and that gives some concern about running the test
with networkserver and cleanup.

Any suggestions on how to handle these issues are welcome...

> 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:
>            Reporter: Knut Anders Hatlen
>            Priority: Minor
> 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.

View raw message