SocketRstTest fails due to exception message check
Motivation: For lack of a better way the SocketRstTest inspects the content of the exception message to check if a RST occurred. However on windows the exception message is different than on other Unix based platforms and the assertion statement fails. Modifications: - Hack another string check in the unit test Result: SocketRstTest passes on windows Fixes https://github.com/netty/netty/issues/5335
This commit is contained in:
parent
bbed330468
commit
e200e4811b
@ -35,7 +35,8 @@ import static org.junit.Assert.assertTrue;
|
|||||||
public class SocketRstTest extends AbstractSocketTest {
|
public class SocketRstTest extends AbstractSocketTest {
|
||||||
protected void assertRstOnCloseException(IOException cause, Channel clientChannel) {
|
protected void assertRstOnCloseException(IOException cause, Channel clientChannel) {
|
||||||
if (Locale.getDefault() == Locale.US || Locale.getDefault() == Locale.UK) {
|
if (Locale.getDefault() == Locale.US || Locale.getDefault() == Locale.UK) {
|
||||||
assertTrue("actual message: " + cause.getMessage(), cause.getMessage().contains("reset"));
|
assertTrue("actual message: " + cause.getMessage(),
|
||||||
|
cause.getMessage().contains("reset") || cause.getMessage().contains("closed"));
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user