Issue 3868 in pharo: [Failing Test] 1.3 SocketTest

Status: Accepted
Owner: [hidden email]
Labels: Milestone-1.3

New issue 3868 by [hidden email]: [Failing Test] 1.3 SocketTest
http://code.google.com/p/pharo/issues/detail?id=3868

Only on Hudson.

>>> NetworkTests.Kernel.SocketTest.testClientConnect 3.011 69
>>> NetworkTests.Kernel.SocketTest.testDataReceive 3.01 69
>>> NetworkTests.Kernel.SocketTest.testDataSending 3.008 69
>>> NetworkTests.Kernel.SocketTest.testLocalAddress 3.014 69
>>> NetworkTests.Kernel.SocketTest.testLocalPort 3.007 69
>>> NetworkTests.Kernel.SocketTest.testRemoteAddress 3.008 69
>>> NetworkTests.Kernel.SocketTest.testRemotePort 3.008 69
>>> NetworkTests.Kernel.SocketTest.testServerAccept 3.011 69

Comment #1 on issue 3868 by [hidden email]: [Failing Test] 1.3  
SocketTest
http://code.google.com/p/pharo/issues/detail?id=3868

I think they work, just on the testserver they brake.

- we remove them
- I check the firewall
- I add them when the firewall is configured correctly

Comment #2 on issue 3868 by [hidden email]: [Failing Test] 1.3  
SocketTest
http://code.google.com/p/pharo/issues/detail?id=3868

Name:  
SLICE-Issue-3868-UseLoopBackAddressForSocketTests-SvenVanCaekenberghe.1
Author: SvenVanCaekenberghe
Time: 15 April 2011, 1:38:03 pm
UUID: 6b15379d-365f-408b-9c90-88b43cdd618b
Ancestors:
Dependencies: NetworkTests-SvenVanCaekenberghe.47

SocketTest was using #localHostAddress instead of #loopBackAddress which  
were failing on the CI server;
added some #asSocketAddress conversions to some tests

Updates:
        Status: Closed

Comment #3 on issue 3868 by [hidden email]: [Failing Test] 1.3  
SocketTest
http://code.google.com/p/pharo/issues/detail?id=3868

in 13153