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
Currently a JSON object is printed to stdout which contains details about the files created in the job.
This data can be see in the logs but it is mixed with stderr.
These two data(stdout and stderr) should be persisted is some way outside of the job logs.
The text was updated successfully, but these errors were encountered:
johnbradley
changed the title
Method to receive back stdout from process
Method to receive back stdout from job
Jan 14, 2019
dleehr
changed the title
Method to receive back stdout from job
Clean up logging and output from pods and calrissian process
Mar 7, 2019
Additionally, the above stderr is currently only the operational logging messages that calrissian reports in its logic. The logs from individual CWL CommandLineTools that contain the bulk of the important workflow information are not fetched from the pods.
cwltool by default prints these tool output streams (stdout/stderr) to cwltool's stderr. Unless we have a better idea, we should mirror that behavior.
Currently a JSON object is printed to stdout which contains details about the files created in the job.
This data can be see in the logs but it is mixed with stderr.
These two data(stdout and stderr) should be persisted is some way outside of the job logs.
The text was updated successfully, but these errors were encountered: