-
Notifications
You must be signed in to change notification settings - Fork 219
clean up locks when EasyBuild session is cancelled with signal like SIGTERM #3291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 6 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
a4d7cad
add create_lock, check_lock and remove_lock function + use them in Ea…
boegel 5800437
add clean_up_locks function
boegel 5ed5b8d
make sure it's OK to call remove_lock on a lock that's no longer there
boegel e7f2226
add signal handler 'clean_up_locks_signal_handler' to clean up locks …
boegel 1752c4a
register signal handlers at start of main to clean up locks on receiv…
boegel 52acdb2
removed unused import
boegel 482975a
fix silly typo: exists -> exits
boegel 5675133
Merge branch 'develop' into lock_cleanup
boegel d879cda
add --wait-on-lock-limit and --wait-on-lock-interval configuration op…
boegel 27ab7e0
add final check for lock before giving up with an error when wait lim…
boegel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would expect wait_on_lock to be the max time to wait, not how long between checks. That's what you would normally do in this situation, i.e. specify a max time to wait.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we need a way to limit the time you're waiting for a lock, and the semantics of
--wait-on-lockis a bit weird right now.So, I changed things in d879cda:
--wait-on-lockstill works as before (0(the default) implies no waiting (raise an error if lock is already there), a value implies enabling waiting with interval of specified number of seconds), but is deprecated;--wait-on-lock-limitcan be used to i) enable waiting for lock to be released, ii) specify a maximum waiting time (if set to0is implies no waiting (raise error if lock is there), if set to-1it implies waiting indefinitely);--wait-on-lock-intervalcan be used to specify the interval for re-checking whether the lock has been released (default 60 sec.)