The build can fail just in ClientIT.connectionFailed in some circumstances, in cases where it is possible to bind to port 8080 yet it is also possible to connect to it. One example is when a process running in the machine on MAC is bound to a part that is externally mapped to port 8080. To avoid such a process having to be stopped before building TCP nukleus, it would be desirable to make the test more robust. One way to do this is as follows:
- add
Function<String, InetAddress> resolver to TcpConfiguration with default value "java.net.InetAddress::getByName"
- override from specific test
connectionFailed to change resolution of localhost to ::2 just for that test
The build can fail just in ClientIT.connectionFailed in some circumstances, in cases where it is possible to bind to port 8080 yet it is also possible to connect to it. One example is when a process running in the machine on MAC is bound to a part that is externally mapped to port 8080. To avoid such a process having to be stopped before building TCP nukleus, it would be desirable to make the test more robust. One way to do this is as follows:
Function<String, InetAddress>resolver toTcpConfigurationwith default value"java.net.InetAddress::getByName"connectionFailedto change resolution oflocalhostto::2just for that test