Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.22.0
-
None
-
None
Description
Running jcarder on the contrib unit tests yielded 3 lock inversions in the capacity scheduler. I don't know enough about the scheduler to know if they're problems - they look harmless enough since they seem to all be concerned with the startup code, which probably doesn't run concurrently with other stuff. Attaching the images of the cycles here.