-
Notifications
You must be signed in to change notification settings - Fork 655
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
NullPointerException when retrying task with an input transfer failure #5727
Comments
When there is a IOException, the FilePorter failure generates a ProcessStageException that extends ProcessException. So, this is the reason why Nextflow retries the task execution. However, when there is a failure during the invocation, the task context has not fully generated what makes it not retryable, at least with the resumeOrDie method. In this cases, I think we should retry cleaning the task and invoking again. |
Any chance to include the related error stack trace? there are many in the log file. |
This is the error stacktrace
|
is this meant to be solved by #5723? |
Bug report
A NullPointerException is thrown during a task retry when a failure there is a failure in the foreign file staging of an input file managed by the file porter. (#5690 (comment))
Expected behavior and actual behavior
When a task requires an input file transfer and it fails, Nextflow produces an exception during the
invokeTask
method before generating the task hash, the management of the exception creates a retry but, it fails because the hash is null.Steps to reproduce the problem
The original failure happens when a read timeout exception is produced when transferring a file in an s3 bucket to a working dir in Google Cloud. I have reproduced the same error when using a non-existing file in s3 as task input, and running the pipeline in Google Cloud. When running the same locally the task fails without retrying.
Program output
See attached log.
Environment
The text was updated successfully, but these errors were encountered: