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] Updated: (DERBY-858) ijConnName test output order is non-deterministic.
Date Wed, 11 Nov 2009 15:21:39 GMT

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

Myrna van Lunteren updated DERBY-858:
-------------------------------------

    Attachment: DERBY-858.diff

Attaching a patch for this issue.

I removed the second connection from the _app.properties file in ijConnName.sql and ij5.sql,
(and adjusted comments) and added ijConnName_sed.properties to remove the 08001 and XJ004
errors resulting from connThree and connFour...As a result, I could remove the extra ijConnName
and ij5 masters.

We do lose a tiny bit of information from the test by doing this: an extra 08001 or XJ004
error would go unnoticed, and we don't see the connection 'name' show up in the ij prompt.
I think there are other tests that would catch a change in behavior that would cause an extra
08001 or XJ004. 

I found 2 junit tests that had depencies on hashtable ordering: derbynet.SysinfoTest and derbynet.ServerPropertiesTest.
So I changed the way those tests check for expected values.


> 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
>         Attachments: DERBY-858.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