-
Notifications
You must be signed in to change notification settings - Fork 8
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
Handle tools that returns exit code status 1 in stub
sections.
#40
Comments
Here are the ways I found that prevent the error code when it happens. We can decide together on how to handle it @arnaudbore @gagnonanthony.
or shorter :
|
I find the The |
I also like the |
#40 - Catch exit code in stub of `betcrop/fslbetcrop`
#40 - Catch error in stub for `preproc/eddy` and `preproc/topup` + add stub test
#40 - Catch antsBrainExtraction.sh exit error code in stub-run + add stub test
#40 - Catch exit code error for `betcrop/synthstrip` + stub run test
When running a stub run for testing pipelines, some tools (such as
ANTs
) return anexit code status 1
when calling the help script. Example:nf-core
does provide suggestions on how to deal with this (https://nf-co.re/docs/guidelines/components/modules#capturing-exit-codes), but it seems only to makenextflow
ignore the output of the command, which is not really wanted when we want to make sure the command is available within the container.List of possible solutions from my quick search:
stdout.log
file, and assert it contains more than one line (an unavailable script still returns a singe line output)The text was updated successfully, but these errors were encountered: