-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
NestedWorkAndContextsTestCase#testStartWorkUnsupportedContext fails intermittently on slower machines because nested work is started before test itself invokes barrier.await and therefore execution of second work isn't stopped.
Expected order of threads is:
test – disabled until workA invokes barrier.await())
workA
workB (nested work) – disabled
But sometimes it is:
workA
workB throws Exception
I'm not sure how to fix this correctly but simplest solution seems to be adding Thread.sleep to Work