Skip to content
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

Subworkflow install failure still results in a 0 exit code #3044

Open
jvfe opened this issue Jul 1, 2024 · 2 comments
Open

Subworkflow install failure still results in a 0 exit code #3044

jvfe opened this issue Jul 1, 2024 · 2 comments
Labels
bug Something isn't working high-priority

Comments

@jvfe
Copy link
Member

jvfe commented Jul 1, 2024

Description of the bug

When installing a subworkflow, if tools can't find a module within this subworkflow it raises an error message, but the error code returned at the end is still 0, making it seem like the command succeeded. This is done in order to not break the execution and install the most modules possible.

A solution suggested on the nf-core slack is to have a has_error variable that persists through the execution, so it still finishes installing the modules but returns a non-zero code at the end.

Command used and terminal output

nf-core create --name test --plain --description test --author test
cd nf-core-test
nf-core subworkflows --git-remote https://github.com/jvfe/test-subworkflow-remote install hic_bwamem2
# ERROR    Module 'samtools/merge' not found in list of available modules.
echo $?

System information

No response

@jvfe jvfe added the bug Something isn't working label Jul 1, 2024
@ewels
Copy link
Member

ewels commented Sep 9, 2024

Is this a duplicate of #2928 ?

@jvfe
Copy link
Member Author

jvfe commented Sep 9, 2024

Is this a duplicate of #2928 ?

While similar, I don't think they mention the exact same thing. The issue there seems to be related to the name of the subworkflow (slashes vs underscores). Here the issue I'm trying to point to is the exit code of the install process, which seems to imply a success even though the subworkflow wasn't fully installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working high-priority
Projects
None yet
Development

No branches or pull requests

2 participants