Re: Flaky tests failing with BindException

2016-08-17 Thread Bruce Schuchardt
otal.io> To: geode <dev@geode.incubator.apache.org> Sent: Friday, July 29, 2016 1:21 PM Subject: Flaky tests failing with BindException Many of our flaky tests are flaky because they use AvailablePort or AvailablePortHelper to find randomly available ports. They then later fail with a BindE

Re: Flaky tests failing with BindException

2016-08-17 Thread Kirk Lund
d a bit with the TemporaryFolder >>>>> rule >>>>> and that's very useful as well, specially to clean up after test runs >>>>> and >>>>> to avoid conflicts. >>>>> >>>>> http://junit.org/junit4/javadoc/4.

Re: Flaky tests failing with BindException

2016-08-04 Thread Bruce Schuchardt
cubator.apache.org> Sent: Friday, July 29, 2016 1:21 PM Subject: Flaky tests failing with BindException Many of our flaky tests are flaky because they use AvailablePort or AvailablePortHelper to find randomly available ports. They then later fail with a BindException because the port

Re: Flaky tests failing with BindException

2016-08-01 Thread Kirk Lund
here any possibility of running multiple test same time on that > > machine? > > > > -Hitesh > > > > > > From: Kirk Lund <kl...@pivotal.io> > > To: geode <dev@geode.incubator.apache.org> > > Sent: Friday, July 29, 201

Re: Flaky tests failing with BindException

2016-08-01 Thread Kirk Lund
yFolder.html >>> >>> Just my 2c >>> >>> On Fri, Jul 29, 2016 at 1:54 PM, Hitesh Khamesra < >>> hitesh...@yahoo.com.invalid> wrote: >>> >>> Is there any possibility of running multiple test same time on that >>>> machine? >>>&g

Re: Flaky tests failing with BindException

2016-07-29 Thread Bruce Schuchardt
t: Friday, July 29, 2016 1:21 PM Subject: Flaky tests failing with BindException Many of our flaky tests are flaky because they use AvailablePort or AvailablePortHelper to find randomly available ports. They then later fail with a BindException because the port is already in use by the time t

Re: Flaky tests failing with BindException

2016-07-29 Thread Jens Deppe
M, Hitesh Khamesra < > hitesh...@yahoo.com.invalid> wrote: > > > Is there any possibility of running multiple test same time on that > > machine? > > > > -Hitesh > > > > > > From: Kirk Lund <kl...@pivotal.io> > > To: geode <

Re: Flaky tests failing with BindException

2016-07-29 Thread Nabarun Nag
ity of running multiple test same time on that > > machine? > > > > -Hitesh > > > > > > From: Kirk Lund <kl...@pivotal.io> > > To: geode <dev@geode.incubator.apache.org> > > Sent: Friday, July 29, 2016 1:21 PM > > Subject: Flaky tests fa

Re: Flaky tests failing with BindException

2016-07-29 Thread William Markito
esh...@yahoo.com.invalid> wrote: > Is there any possibility of running multiple test same time on that > machine? > > -Hitesh > > > From: Kirk Lund <kl...@pivotal.io> > To: geode <dev@geode.incubator.apache.org> > Sent: Friday, July 29, 2016 1:21 PM > Subject:

Re: Flaky tests failing with BindException

2016-07-29 Thread Hitesh Khamesra
Is there any possibility of running multiple test same time on that machine? -Hitesh From: Kirk Lund <kl...@pivotal.io> To: geode <dev@geode.incubator.apache.org> Sent: Friday, July 29, 2016 1:21 PM Subject: Flaky tests failing with BindException Many of our flaky tes

Re: Flaky tests failing with BindException

2016-07-29 Thread Kenneth Howe
Sounds like it would improve the results, but not necessarily fix, BindException @Flaky test failures. Even after n number of retries we’d still not be sure of finding the requested port available. Has any testing been done to find a point of diminishing returns on increasing the retry count?

Flaky tests failing with BindException

2016-07-29 Thread Kirk Lund
Many of our flaky tests are flaky because they use AvailablePort or AvailablePortHelper to find randomly available ports. They then later fail with a BindException because the port is already in use by the time the test uses it. Here's a proposal for a temporary fix: The module geode-junit