Repository navigation
Conversation
Creating a gfal2 context leaves most signals (SIGTERM, SIGINT, SIGQUIT, SIGALRM, ...) blocked in the calling thread. The payload inherits the signal mask of the thread that starts it, so it couldn't be stopped with SIGTERM, and Gaudi's EventWatchdog could not abort stuck jobs with SIGQUIT (gaudi/Gaudi#428).
chrisburr
force-pushed
the
fix/reset-signal-mask-for-payload-integration
branch
from
October 20, 2026 12:43
869da71 to
77e4a55
Compare
This branch has not been deployed
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
1 participant
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.
Port of #8838 to integration.
BEGINRELEASENOTES
*WorkloadManagement
FIX: the payload no longer inherits signals blocked in the JobWrapper (e.g. by gfal2), so it can be stopped with SIGTERM and abort itself with SIGQUIT
ENDRELEASENOTES