On 09-04-13 11:44, Peter Firmstone wrote:
I've never experienced the issue locally (I see it on Jenkins quite a
lot), but I suspect a stale registrar process left from another test may
be stopping the socket from closing. Not that registrars are also
simulated for discovery tests, so it may not necessarily be Reggie.
The code is duplicated in two places in superclasses of the tests that
are failing, the method portInUse(int port) is supposed to check if the
ports available, but only selects from a list of LookupLocator's known
to have started, so doesn't actually check the port's available.
Perhaps you can find the stale test process responsible?
And other jobs get executed on the same machine at the same time. Maybe
these consume ports?
The best way to find the problem looks to me like doing a 'lsof -i' in
the test as soons as a port turns out used unexpectedly.
Gr. Simon
--
QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397
