Closed julianladisch closed 6 years ago
What if we started with random ports? (e.g., listen()
)
@jponge this is a solution to heal the consequence of a leak in tests, if you leave a port open it means you are also leaking descriptors, so you should rather try to find the root cause of the bind error
Sometimes the port has been closed, but you still can have a bind error because you try to bind again too fast.
On 29 Oct 2018, at 15:16, Julien Viet notifications@github.com wrote:
@jponge this is a solution to heal the consequence of a leak in tests, if you leave a port open it means you are also leaking descriptors, so you should rather try to find the root cause of the bind error
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
if you close vertx in shutdown of the test and wait until the async result of the close operation is completed, it should work
I’ll check that
On 29 Oct 2018, at 18:23, Julien Viet notifications@github.com wrote:
if you close vertx in shutdown of the test and wait until the async result of the close operation is completed, it should work
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
that's what we do in vertx-core with 2200 tests :-)
Need to dig more, the extension is already waiting for the Vertx context to close.
On 29 Oct 2018, at 18:47, Julien Viet notifications@github.com wrote:
that's what we do in vertx-core with 2200 tests :-)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I found the culprit in test ;-)
Fixed in master
. Thanks @julianladisch for reporting!
good job Sherlock
On my slow laptop
mvn surefire:test
always runs successfully butmvn surefire:test -Dtest=*
always fails.The failure is in IntegrationTest only. It fails with one out of these four failure message types: