You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
Hello,
This is a suggestion to help debug when running conformance tests. cwltest appends "--quiet" to the command line.
cwltest/cwltest/__init__.py
Line 64 in 65ec76c
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.
The text was updated successfully, but these errors were encountered: