You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a CWL in which a node produces an output that saves into a std.out file (defined as stdout: std.out), and the following node uses the content of this file.
The execution of this CWL on ADES (endpoint https://localhost/pml/wps3/processes/) fails between the end of the first node and the following node, because the content of the std.out file is empty (despite in the log of the first node it is shown the printed results).
A temporary workaround could be to rename, in the first node, the output file differently from std.out. But perhaps this could be handled differently / more efficiently from the ADES execution code?
The text was updated successfully, but these errors were encountered:
I have a CWL in which a node produces an output that saves into a std.out file (defined as stdout: std.out), and the following node uses the content of this file.
The execution of this CWL on ADES (endpoint https://localhost/pml/wps3/processes/) fails between the end of the first node and the following node, because the content of the std.out file is empty (despite in the log of the first node it is shown the printed results).
This seems to be caused by this row 96, https://github.com/EOEPCA/proc-workflow-executor/blob/develop/src/workflow_executor/execute.py#L96], which deletes the content of the file defined exactly as "stdout: std.out".
A temporary workaround could be to rename, in the first node, the output file differently from std.out. But perhaps this could be handled differently / more efficiently from the ADES execution code?
The text was updated successfully, but these errors were encountered: