Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.5.0
-
None
-
None
-
None
Description
TestContainerReuse and TestTaskScheduler use a mechanism to get notified when a scheduler run completes.
However, there seems to be a race where a scheduling run may already have started, after which a request is made for an allocation / containers are allocated. The request ends up being skipped in the current scheduling run; meanwhile the notification mechanism signals completion.