[
https://issues.jboss.org/browse/WFCORE-3539?page=com.atlassian.jira.plugi...
]
Brian Stansberry edited comment on WFCORE-3539 at 1/23/18 3:34 PM:
-------------------------------------------------------------------
[~honza889] Sure, that would be better, particularly if it is easy to set up and avoids
conflicts with random other stuff that may be on the machine. Note that it's different
ports per test method not just per test class. The failures are usually within the same
class.
Also, I thought about looping through a set of expected-to-be ok ports (rather than just
blindly incrementing and hoping you don't hit a conflict) but a caveat is I've
observed that just a 50 ms sleep still produced failures. 100 ms seemed ok, at least on
ci.wildfly.org. So any set of "ok ports" would have to be big enough to allow
enough tests to run and time to pass before starting over.
was (Author: brian.stansberry):
[~honza889] Sure, that would be better, particularly if it is easy to set up and avoids
conflicts with random other stuff that may be on the machine. Note that it's different
ports per test method not per test class. The failures are usually within the same class.
Flunky controller tests on Windows: Address already in use
----------------------------------------------------------
Key: WFCORE-3539
URL:
https://issues.jboss.org/browse/WFCORE-3539
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Affects Versions: 4.0.0.Alpha6
Reporter: Jan Kalina
Assignee: Jan Kalina
Following combination of tests will fail *sometimes* on "Address already in use:
bind" on windows:
{code}
mvn test
-Dtest=org.jboss.as.controller.test.RemoteChannelProxyControllerTestCase,org.jboss.as.controller.test.TransactionalProtocolClientTestCase
{code}
{code}
[Step 2/3] org.jboss.as.controller.test.TransactionalProtocolClientTestCase
[21:41:55][org.jboss.as.controller.test.TransactionalProtocolClientTestCase]
testSequentialGroup
[21:41:55][org.jboss.as.controller.test.TransactionalProtocolClientTestCase]
testCancelBeforePrepared
[21:41:55][testCancelBeforePrepared] java.net.BindException: Address already in use:
bind
[21:41:55]
[testCancelBeforePrepared] java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:433)
at sun.nio.ch.Net.bind(Net.java:425)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at org.xnio.nio.NioXnioWorker.createTcpConnectionServer(NioXnioWorker.java:181)
at org.xnio.XnioWorker.createStreamConnectionServer(XnioWorker.java:310)
at
org.jboss.remoting3.remote.RemoteConnectionProvider$ProviderInterface.createServer(RemoteConnectionProvider.java:372)
at org.jboss.as.controller.support.ChannelServer.create(ChannelServer.java:93)
at
org.jboss.as.controller.test.TransactionalProtocolClientTestCase.startChannelServer(TransactionalProtocolClientTestCase.java:108)
{code}
This happens pretty often on windows CI:
https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&...
But it is sufficient to run combination of tests above on Windows to reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)