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

logging of debug messages not possible since --quiet hardcoded in cwltest #64

Open
pkp124 opened this issue Apr 5, 2018 · 1 comment

Comments

@pkp124
Copy link

pkp124 commented Apr 5, 2018

Hello,

This is a suggestion to help debug when running conformance tests. cwltest appends "--quiet" to the command line.

"--quiet",

Also, removing "--quiet" in cwltest makes all test cases fail, probably because the output of executor is obtained from stdout.
When running conformance tests, enabling debug messages and logging them is no longer an option from the command line.

One suggestion is to provide an option for cwltool to write the output of executor to a file instead of stdout. This enables cwltest to compare output from a specified file instead of disabling debug messages to get output string from stdout.

@mr-c
Copy link
Member

mr-c commented May 3, 2018

Hello @pkp124, we do preserve stderr and that gets reported in the junit xml.

If there is reporting to stdout from cwltool and others even without --quiet then I'd consider that a bug that needs fixing. Once that is done we should be able to safely remove --quiet.

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

2 participants