-
-
Notifications
You must be signed in to change notification settings - Fork 34
Open
Description
Just had a case where manually aborting a job did not release the mutex.
Have not tracked down the specifics yet, but, regardless it happened.
Things I noticed were:
- Not clear how to tell what job is the owner of the mutex
- What's the appropriate action to take to release the lock? (Other than simply deleting the branch)
This does make me want:
- Max wait timeout. In case an aborted job fails to release the mutex again, this would let the next in line caller force the issue and take ownership.
- A notification channel for cases where the above happens
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels