Skip to content
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

Inconsistent logging in rt.sh Rocoto mode #2207

Closed
SamuelTrahanNOAA opened this issue Mar 24, 2024 · 0 comments · Fixed by #2202
Closed

Inconsistent logging in rt.sh Rocoto mode #2207

SamuelTrahanNOAA opened this issue Mar 24, 2024 · 0 comments · Fixed by #2202
Labels
bug Something isn't working

Comments

@SamuelTrahanNOAA
Copy link
Collaborator

Description

The destinations of stderr and stdout are inconsistent between rt.sh modes.

  1. With ecFlow, stdout and stderr go to the compile*.log files, but with Rocoto only stdout goes there.
  2. Rocoto sends stderr to the test job log files, but not stdout (that file is empty).
  3. 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:

  1. Rocoto matches the ecFlow behavior and sends stdout and stderr together to compile*.log files.
  2. Rocoto sends both stderr and stdout to job log files.
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant