db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-858) ijConnName test output order is non-deterministic.
Date Mon, 23 Jan 2006 19:41:09 GMT
ijConnName test output order is non-deterministic.
--------------------------------------------------

         Key: DERBY-858
         URL: http://issues.apache.org/jira/browse/DERBY-858
     Project: Derby
        Type: Test
  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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message