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-1247) test DerbyNetAutoStart uses non-portable mechanism to check on derby.log
Date Thu, 27 Apr 2006 04:08:06 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1247?page=comments#action_12376628 ] 

Myrna van Lunteren commented on DERBY-1247:

This can be cleanly merged into 10.1:

merge command:
>svn merge -r 397299:397300 https://svn.apache.org/repos/asf/db/derby/code/trunk

I tested the test derbynet/DerbyNetAutoStart.java before and after the merge (& subsequent
build) with jdk14 on windows and ibm14 on zOS. On zOS before the test fails, and after, passes.

> test DerbyNetAutoStart uses non-portable mechanism to check on derby.log
> ------------------------------------------------------------------------
>          Key: DERBY-1247
>          URL: http://issues.apache.org/jira/browse/DERBY-1247
>      Project: Derby
>         Type: Bug

>   Components: Test
>     Versions:
>  Environment: zOS
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>      Fix For:
>  Attachments: DERBY-1247_102_20060422.diff
> The test DerbyNetAutoStart uses RandomAccessFile.readLine() on derby.log to find an occurrence
of a String[] to decide whether the tests passes or not.
> This mechanism assumes that derby.log is in Unicode-compatible encoding, which may not
be true.
> Also, readLine() documentation indicates that it does not support the 'full Unicode range',
so may not be the best choice.
> And indeed, the test fails on zOS, even though the string looked for is present in derby.log.

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