You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Myrna van Lunteren (JIRA)" <ji...@apache.org> on 2014/03/07 04:35:44 UTC

[jira] [Resolved] (DERBY-5942) Assert failure in derbynet.NetworkServerControlClientCommandTest.testPingWithWrongHost

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

Myrna van Lunteren resolved DERBY-5942.
---------------------------------------

    Resolution: Cannot Reproduce

I was hesitating between marking this one as 'fixed' because a change went in, Kristian reported this as reproducible, and I ran the test 100x with 10.10 and it did not fail.

But looks like Kristian did not actually expect the change to fix the problem, so I'm marking it Cannot Reproduce instead. As always, if the problem resurfaces, this issue can be reopened.

> Assert failure in derbynet.NetworkServerControlClientCommandTest.testPingWithWrongHost
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-5942
>                 URL: https://issues.apache.org/jira/browse/DERBY-5942
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>         Environment: ARM processor, Ubuntu Linux Highbank, Java SE Embedded 1.7.0_06-b24
>            Reporter: Kristian Waagan
>            Priority: Minor
>         Attachments: derby-5942-1a-rfc2606.diff
>
>
> The test derbynet.NetworkServerControlClientCommandTest.testPingWithWrongHost fails in an assert (line 112):
> junit.framework.AssertionFailedError: Could not find expectedString:Unable to find host in output:<STDOUT>Sat Sep 29 19:04:59 CDT 2012 : Could not connect to Derby Network Server on host nothere, port 1527: Connection timed out
> The failure is reproducible.



--
This message was sent by Atlassian JIRA
(v6.2#6252)