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] Resolved: (DERBY-858) ijConnName test output order is non-deterministic.
Date Thu, 12 Nov 2009 18:30:39 GMT

     [ https://issues.apache.org/jira/browse/DERBY-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren resolved DERBY-858.
--------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.6.0.0
                      10.5.3.1
    Issue & fix info:   (was: [Patch Available])

committed to trunk with revision 835153 and backported to 10.5 with revision  835482.
Interesting svn quirk: the merged added file didn't show up when I did svn diff on 10.5. But
it was there with svn stat and it seems to have been correctly added.

> 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
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.5.3.1, 10.6.0.0
>
>         Attachments: DERBY-858.diff, DERBY-858.diff2, DERBY-858_105.diff
>
>
> 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.


Mime
View raw message