db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4035) i18n tests fail with Lexical error on z/os
Date Fri, 03 Jul 2009 11:29:47 GMT

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

Knut Anders Hatlen updated DERBY-4035:
--------------------------------------

           Component/s:     (was: Tools)
                        Test
               Urgency: Normal
    Bug behavior facts: [Regression Test Failure]

Triaged for 10.5.2. Changing component to Test since the discussion indicates this is a problem
with the old test harness.

> i18n tests fail with Lexical error on z/os 
> -------------------------------------------
>
>                 Key: DERBY-4035
>                 URL: https://issues.apache.org/jira/browse/DERBY-4035
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.3.3.0, 10.5.1.1
>         Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz6460sr3-20081108_01(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390x-64 jvmmz6460-20081107_25433 (JIT
enabled, AOT enabled)
> J9VM - 20081105_025433_BHdSMr
> JIT  - r9_20081031_1330
> GC   - 20081027_AB)
> JCL  - 20081106_01
> $
>            Reporter: Kathey Marsden
>
> On z/os  the following tests fail with a Lexical error e.g.
>  ERROR 42X02: Lexical error at line 1, column 1.  Encountered: "`" (96), after : "".
 There also seems to be some garbage in the output.  The tests that fail with these errors
are:
> derbyall/derbyall.fail:i18n/JapanCodeConversion.sql
> derbyall/derbyall.fail:i18n/UnicodeEscape_JP.sql
> derbyall/derbyall.fail:i18n/I18NImportExport.sql
> derbyall/derbyall.fail:i18n/urlLocale.sql
> derbyall/derbyall.fail:i18n/messageLocale.sql
> derbyall/derbyall.fail:i18n/caseI_tr_TR.sql
> derbyall/derbyall.fail:i18n/iepnegativetests_ES.sql
> The error I think is coming from ij, it is not in the derby.log and there is not a stack
trace anywhere.

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