Use -d flag for bkill in LSF Executor#6784
Open
cgoina wants to merge 1 commit intonextflow-io:masterfrom
Open
Conversation
✅ Deploy Preview for nextflow-docs-staging canceled.
|
cgoina
force-pushed
the
lsf-bkill-flag
branch
from
fff08fe to
6004f11
Compare
cgoina
force-pushed
the
lsf-bkill-flag
branch
from
6004f11 to
5478c63
Compare
Signed-off-by: Cristian Goina <goinac@janelia.hhmi.org>
cgoina
force-pushed
the
lsf-bkill-flag
branch
from
5478c63 to
cbac689
Compare
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.
This is the PR for #6772 to add '-d' flag when killing the LSF job. Our cluster admins suggested that this is the correct behavior because even if Nextflow kills the LSF job from the LSF scheduler's perspective the job was terminated as intended.
I've been running this on our LSF cluster and it looks good.