db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-858) ijConnName test output order is non-deterministic.
Date Mon, 09 Nov 2009 22:47:32 GMT

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

Myrna van Lunteren commented on DERBY-858:

ij5.sql has the same problem.
If the hash table ordering is different, this may result in ConnTwo being the first connection
made, and so the active connection.

I think it's ok for these two tests to not have the 2nd valid pre-defined connection. Does
anyone disagree?

> ijConnName test output order is non-deterministic.
> --------------------------------------------------
>                 Key: DERBY-858
>                 URL: https://issues.apache.org/jira/browse/DERBY-858
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>            Reporter: Daniel John Debrunner
>            Priority: Minor
> The test loads four initial connections using these ij.connection properties in the test's
_app.properties file.
> ij.connection.connOne=jdbc:derby:wombat;create=true
> ij.connection.connTwo=jdbc:derby:lemming;create=true
> ij.connection.connThree=jdbc:noone:fruitfly;create=true
> ij.connection.connFour=jdbc:derby:nevercreated
> The order these connections are created, and hence the order of the test output is only
determined by the hash table ordering of the properties file. Making small changes in  ijConnName_app.properties
files can change the order, making the test appear to fail.
> E.g. I tried to enable the test with a security manager by modifying the noSecurityManger
to be set to false, and the order changed.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message