ly work because they work on left-overs from previous tests. This is
> pretty dangerous and should get fixed asap.
> >
> > I didn't touch them yet because I first like to get the IT on our CI box
> working again.
> >
> > LieGrue,
> > strub
> >
>
tephen Connolly
wrote:
>
>> From: Stephen Connolly
>> Subject: Re: Random errors in parallely executed tests
>> To: "Maven Developers List"
>> Date: Sunday, July 31, 2011, 6:28 PM
>> the buildhelper goal is for when you
>> are launching jetty/etc from the
gt; Subject: Re: Random errors in parallely executed tests
> To: "Maven Developers List"
> Date: Sunday, July 31, 2011, 6:28 PM
> the buildhelper goal is for when you
> are launching jetty/etc from the pom.
> or when you need to filter the port into on disk
> resources.
the buildhelper goal is for when you are launching jetty/etc from the pom.
or when you need to filter the port into on disk resources.
if launching within the test case, just assign it to port 0. a request for
port 0 is a request for an unused port in the top 16k (or depending on the
os, anywhere
the same exists for the serving port.
>
> LieGrue,
> strub
>
> --- On Sun, 7/31/11, Olivier Lamy wrote:
>
>> From: Olivier Lamy
>> Subject: Re: Random errors in parallely executed tests
>> To: "Maven Developers List"
>> Date: Sunday, July 31, 20
ah, I knew you did something like this but could not find it :)
question: ok, random port, but random and guaranteed to success? ie it makes
the effort to find an unused port?
see r1152587: I chose an arbitrary port
we should add this to a FAQ, since this is a common use case
Regards,
Hervé
L
ier Lamy
> Subject: Re: Random errors in parallely executed tests
> To: "Maven Developers List"
> Date: Sunday, July 31, 2011, 3:55 PM
> Hello
> Jetty is normally able to start on a random port.
> I have fixed that recently in archetype.
> Imho better solut
Hello
Jetty is normally able to start on a random port.
I have fixed that recently in archetype.
Imho better solution.
Which tests fail for this reason ?
--
Olivier
send from a mobile
Le 31 juil. 2011 17:43, "Mark Struberg" a écrit :
> Hi!
>
> While browsing our CI results I saw randomly failing
Hi!
While browsing our CI results I saw randomly failing tests. Most of them are
caused by starting jetty on a specific port which already is in use by another
test.
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind(Native Method)
Clearly if 2 unit tests fire up a j
