You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes in test logs there would be an exception raised by queue object serving the role of management queue. This exception is caused by calling .join() by thread on itself, which means that last ocf_queue_put is called from code executed on this queue which shouldn't happen. Most possibly it is an error with pyocf handling of queue lifetime.
The text was updated successfully, but these errors were encountered:
OCF cache does not put management queue on stop. It is adapter responsibility to put management queue after cache is stopped. Typically this must not be done from outside of cache stop completion callback, as this might run in management queue context.
I don't understand what triggers the problematic queue_put(). This remains to be investigated.
Description
Sometimes in test logs there would be an exception raised by queue object serving the role of management queue. This exception is caused by calling
.join()
by thread on itself, which means that lastocf_queue_put
is called from code executed on this queue which shouldn't happen. Most possibly it is an error with pyocf handling of queue lifetime.The text was updated successfully, but these errors were encountered: