[
https://issues.apache.org/jira/browse/DERBY-5942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5942:
-----------------------------------
Attachment: derby-5942-1a-rfc2606.diff
Attached patch 1a, which brings the invalid host in accordance with RFC 2606.
I don't expect that this will make the failure go away, since that didn't
happen for DERBY-5941.
Committed to trunk with revision 1393462.
> 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 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
