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
The destinations of stderr and stdout are inconsistent between rt.sh modes.
With ecFlow, stdout and stderr go to the compile*.log files, but with Rocoto only stdout goes there.
Rocoto sends stderr to the test job log files, but not stdout (that file is empty).
Rocoto combines the stdout and stderr streams of compiles into a .log file, but splits the test jobs into .err and (empty) .out files.
I suggest:
Rocoto matches the ecFlow behavior and sends stdout and stderr together to compile*.log files.
Rocoto sends both stderr and stdout to job log files.
Rocoto combines stderr and stdout into one stream for job log files. This way, we don't lose the context of what errors go with what output. The separate out & err streams are in out & err files in the job's work directory if someone needs separate files.
To Reproduce:
Run rt.sh in Rocoto and ecFlow modes.
The text was updated successfully, but these errors were encountered:
Description
The destinations of stderr and stdout are inconsistent between rt.sh modes.
I suggest:
To Reproduce:
Run rt.sh in Rocoto and ecFlow modes.
The text was updated successfully, but these errors were encountered: