db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-575) test blobclob4BLOB fails on OS 390
Date Mon, 19 Sep 2005 13:23:30 GMT
    [ http://issues.apache.org/jira/browse/DERBY-575?page=comments#action_12329842 ] 

Myrna van Lunteren commented on DERBY-575:

Unfortunately, you *do* have to convert most of the text files used by the various tests.
Certainly all master files, and for instance text files for import/export.

I unraveled derbyTesting.jar,  used native2ascii  -reverse in a script on the os390 machine
to convert to Cp1047 and jar-ed it back up (for space).

> test blobclob4BLOB fails on OS 390
> ----------------------------------
>          Key: DERBY-575
>          URL: http://issues.apache.org/jira/browse/DERBY-575
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions:
>  Environment: OS/390 (z/OS 1.06; IBM j2RE 1.4.2)
>     Reporter: Myrna van Lunteren
>     Priority: Minor
>      Fix For:

> The subtest clobNegativeTest_Derby265 in test jdbcapi/blobclob4BLOB assumes that the
length of the file used (aclob.txt) is 300000 but on OS 390 (z/OS), after conversion to EBCDIC,
the length is 297000. The test should be modified to not use a hardcoded size.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message