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] Updated: (DERBY-1247) test DerbyNetAutoStart uses non-portable mechanism to check on derby.log
Date Sun, 23 Apr 2006 06:34:06 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1247?page=all ]

Myrna van Lunteren updated DERBY-1247:

    Attachment: DERBY-1247_102_20060422.diff

The attached patch for the trunk - DERBY-1247_102_20060422.diff - affects only the test derbynet/DerbyNetAutoStart.java
With this change, the test passes for me both with DerbyNet and DerbyNetClient, both on windows
and zOS.
I don't see any point in running derbyall (I did check that the changed method checkLog was
not used in any other test).

The patch should merge cleanly to the trunk.

> 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