db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3838) Convert derbynet/DerbyNetAutoStart to JUnit
Date Fri, 22 Mar 2013 04:15:21 GMT

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

Dag H. Wanvik commented on DERBY-3838:
--------------------------------------

Thanks, Myrna! For me the test took over 4 minutes to finish: in line
ca 250 I see this code:

   // Check the server is still up 
   assertTrue(NetworkServerTestSetup.pingForServerUp(ns, null, false));

Should it be "true" here for the argument "expectServerUp" (since we expect the server to
still be up)? If I substitute with "true", the test runs quickly... It seems all pingForServerUp
does if the argument is "false" is sit around for 4 minutes observing the server is (still)
up and then returns true...

                
> Convert derbynet/DerbyNetAutoStart to JUnit
> -------------------------------------------
>
>                 Key: DERBY-3838
>                 URL: https://issues.apache.org/jira/browse/DERBY-3838
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.5.1.1
>            Reporter: Erlend Birkenes
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>         Attachments: DERBY-3838_2.diff, DERBY-3838.diff, DERBY-3838.diff
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message