Re: unit test failures
Philip Aston <[email protected]> Sun, 01 Apr 2012 15:15:49 +0100
| Newsgroups | gmane.comp.java.grinder.devel |
|---|---|
| Message-ID | <[email protected]> |
Interesting. They both work for me on linux / jdk160_21. Can you actually resolve "unknownhost" (nslookup unknonwnhost)? - Phil On 27/03/12 18:49, Bill Smith wrote: > I noticed two unit test failures in grinder.http. Both fail in the > same way: they try to open a socket on a restricted port (port 222) > and expect to catch an java.net.UnknownHostException, when in fact the > exception is java.net.BindException. > > The tests are: > * > net.grinder.tools.tcpproxy.TestHTTPProxyTCPProxyEngine/testBadLocalPort and > * > net.grinder.tools.tcpproxy.TestPortForwarderTCPProxyEngine/testBadLocalPort. > > > Observed this in release_3.8 with JRE 1.6 on Linux. > > Bill > > P.S. Nice to see unit tests in the project. ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure