[bugfix] Properly treat forceful termination due to SIGTERM and SIGHUP#3534
Merged
vkarak merged 2 commits intoreframe-hpc:masterfrom Jul 25, 2025
Merged
[bugfix] Properly treat forceful termination due to SIGTERM and SIGHUP#3534vkarak merged 2 commits intoreframe-hpc:masterfrom
SIGTERM and SIGHUP#3534vkarak merged 2 commits intoreframe-hpc:masterfrom
Conversation
vkarak
force-pushed
the
bugfix/handle-sighup
branch
from
22be2a4 to
a4b1ce9
Compare
teojgo
approved these changes
Jul 25, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
ReFrame was not exiting gracefully if it received the
SIGHUPsignal. This is now treated as theSIGTERM. However, there are scenarios, especially when run through Gitlab CI, that ReFrame receives both signals in random order and in close timing. This was problematic as ReFrame was interrupted while having initiated its shutdown. For this reason, the signal handler for both of these signals ignores any interrupt or force-exit signals until ReFrame gracefully exits.@ekouts This will likely eliminate the need for #3459.