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
When cwltool is executed, standard output of cwltool, standard error output, output of each tool is dumped.
When log is collected by redirect,
stdout: stdout of cwltool
stderr: stderr of cwltool and output of each tool
This is not supposed to be the expected behavior.
Of course, the output of each tool should be written in the tool definition. However, if we prepare log collecting methods other than redirects, will not logs get mixed up?
As described above, the log output in the case of collecting by using main.py directly is originally supposed. Therefore, it seems to be necessary to prepare a log collection method other than redirect.
Though I don't know if the current behavior of cwltool to output the mixed stderr log of each tool and cwltool itself is intentional, it'd be good if users can specify files to write the stderr separately.
If there's no blocker to implement these options, @suecharo would help to implement it ;) Any idea for logging, @mr-c@tetron ?
Expected Behavior
Actual Behavior
When cwltool is executed, standard output of cwltool, standard error output, output of each tool is dumped.
When log is collected by redirect,
This is not supposed to be the expected behavior.
Of course, the output of each tool should be written in the tool definition. However, if we prepare log collecting methods other than redirects, will not logs get mixed up?
When collected by redirect
stdout.log
stderr.log
When collecting using
main.py
directlystdout.log
stderr.log
As described above, the log output in the case of collecting by using
main.py
directly is originally supposed. Therefore, it seems to be necessary to prepare a log collection method other than redirect.Workflow Code
Using https://github.com/hacchy1983/CWL-workflows
Your Environment
Ubuntu: 16.04
The text was updated successfully, but these errors were encountered: