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

Log file in case of failure #14

Open
fginter opened this issue Nov 4, 2014 · 3 comments
Open

Log file in case of failure #14

fginter opened this issue Nov 4, 2014 · 3 comments

Comments

@fginter
Copy link
Member

fginter commented Nov 4, 2014

The stderr of the pipeline components should be redirected to a log file, whose location is shown to the user in case of failure. This should help us debug spurious failures of the parser.

@spyysalo
Copy link
Contributor

spyysalo commented Nov 4, 2014

May I suggest using the python logging system instead of print to stderr? It's really easy to get started with and quite flexible.

@fginter
Copy link
Member Author

fginter commented Nov 4, 2014

Most of the pipeline components are not even Python, but external programs. The stderr output needs to be gathered on the bash side. We do use Python logging module (occasionally ;).

@spyysalo
Copy link
Contributor

spyysalo commented Nov 4, 2014

Humbly withdrawn :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants