db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-1914) test lang/wisconsin gives garbage output on zOS.
Date Thu, 28 Jun 2012 19:38:44 GMT

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

Kathey Marsden commented on DERBY-1914:

actually, I think not. I realize this would mean bringing jakarta into the set of jars required
to run JUnit tests, so I think not a good idea.

> test lang/wisconsin gives garbage output on zOS.
> ------------------------------------------------
>                 Key: DERBY-1914
>                 URL: https://issues.apache.org/jira/browse/DERBY-1914
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:,,
>         Environment: ibm 15 jvm on z/OS (aka z-series, or OS/390)
> also
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz3160sr5-20090604_01(SR5))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390-31 jvmmz3160sr5-20090519_3
> 5743 (JIT enabled, AOT enabled)
> J9VM - 20090519_035743_bHdSMr
> JIT  - r9_20090518_2017
> GC   - 20090417_AA)
> JCL  - 20090529_01
> (output attached)
>            Reporter: Myrna van Lunteren
>            Assignee: Kathey Marsden
>              Labels: derby_triage10_8
>         Attachments: derby-1914_diff.txt, wisconsinOutputAfterAsciiFtp.zip, wisconsinOutputOnZos.zip
> When running the test lang/wisconsin.java on zOS the output in the .tmp file shows non-native
> However, this is most likely a test/test harness specific problem, for if one executes
the simple statistics gathering commands through ij, there is no problem. Note that other
tests do produce readable (native) output.
> It's impossible to tell if there is any actual problem this way. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message