This raises a more general question that has been troubling me: What
should we do about theoretical deadlocks and similar concurrency issues
that have not been demonstrated in practice?
On the one hand, I like to have a test to show that a change really
fixed something. On the other hand, a concurrency problem can contribute
to general flakiness without ever reaching the point of being reported
as a bug or having a test that demonstrates it.
Patricia
On 5/4/2011 8:47 AM, Christopher Dolan wrote:
...
I haven't conclusively witnessed that specific deadlock, but I've had a
closely related problem where another process coincidentally grabs port
4160 before Reggie gets it. This happens because Win2k, WinXP and Win2k3
use 1024-5000 for their dynamic port range, contrary to IANA
recommendations. I suspect the deadlock described above happens in real
life, but I've never gotten detailed enough logs to prove it, just
client stack traces showing the hang in Mux.start().
...
