Hi, guys.
Igor is absolutelly right - there are no deadlocks. We have only warnings
from detector, but they caused by difference between actual locking order
in the code and allowed by detector. It is annoying, but detection is used
only in development environment, thus it is not high bug.
When
Hey Vitaly,
Are you the problem is in deadlock? I see the deadlock detecter
traceback, but not an actual deadlock.
I'm not sure could it be a reason for failure or not, it's better to
ask Alexander Kislitsky.
Thanks,
Igor
On Wed, Dec 30, 2015 at 2:57 PM, Vitaly Kramskikh
Hi,
We have a long-living issue with deadlocks in nailgun which used to almost
harmless and caused rare test failures. But test failures become more
frequent and today there is ~20% probability that they will fail on a
working code, which is really annoying. Moreover, a few weeks ago it
started
Alexander,
Thanks for the response.
As for tasks hanging bug, I removed "deadlock" from its title: there is
another exception, which I didn't find due to huge number of traces from
deadlock detector.
As for random test failures bugs, I totally agree we should focus on them.
Just look at this:
