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

add to log when running with --continue #71

Closed
toddr opened this issue Mar 29, 2022 · 0 comments · Fixed by #86
Closed

add to log when running with --continue #71

toddr opened this issue Mar 29, 2022 · 0 comments · Fixed by #86
Assignees

Comments

@toddr
Copy link
Member

toddr commented Mar 29, 2022

specify in log that a continue has been triggered when it happens?

@sloanebernstein sloanebernstein self-assigned this Apr 6, 2022
sloanebernstein added a commit that referenced this issue Apr 7, 2022
The log file should record when a stage is retried via --continue.

Implements #71.
@sloanebernstein sloanebernstein linked a pull request Apr 7, 2022 that will close this issue
sloanebernstein added a commit that referenced this issue Apr 8, 2022
The log file should record when a stage is retried via --continue.

Implements #71.
sloanebernstein added a commit that referenced this issue Apr 11, 2022
Originally, logging to a file was done by piping screen output to
`tee(1)`. This prevented some output from being logged, as only the
systemd service did this. Instead, use a native log4perl file appender
to log to the file.

This eliminates colored output, since there is no direct way to save
color data to the file anymore. Restoring this feature will be explored
in a future issue.

Resolves #71 and #83.
@toddr toddr closed this as completed in #86 Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants