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

Print errors to STDERR #319

Open
Jeltje opened this issue Jun 24, 2016 · 2 comments
Open

Print errors to STDERR #319

Jeltje opened this issue Jun 24, 2016 · 2 comments

Comments

@Jeltje
Copy link
Contributor

Jeltje commented Jun 24, 2016

I know this is true for rnaseq_cgl and ProTECT (filed a ticket there, too): when the program exits with an error, it is printed to STDOUT. The same is true for warnings. This makes it harder to find the problem (there's a lot of log output) and it also doesn't seem to be good practice.

@hannes-ucsc
Copy link
Contributor

All errors should be logged logging package, not printed, and logging should be configured to write to sys.stderr. This might be a Toil issue, actually, but before we go down that route, I would like this issue to be verified.

@jvivian
Copy link
Collaborator

jvivian commented Jun 28, 2016

In all production pipelines there is now only use of job.fileStore.logToMaster

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

No branches or pull requests

3 participants