-
Notifications
You must be signed in to change notification settings - Fork 52
Unwanted output in tests (and probably outside of it, too) #392
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
Labels
Comments
I fully agree with you. Libraries should not print directly to stdout/stderr. |
Related issue: uuverifiers/ostrich#95 |
kfriedberger
added a commit
that referenced
this issue
Mar 8, 2025
This is a first step for #392 . The situation is also reported to Ostrich in uuverifiers/ostrich#95 .
kfriedberger
added a commit
that referenced
this issue
Mar 8, 2025
This is a first step for #392 . The situation is also reported to Ostrich in uuverifiers/ostrich#95 .
kfriedberger
added a commit
that referenced
this issue
Mar 8, 2025
This is a first step for #392 . The situation is also reported to Ostrich in uuverifiers/ostrich#95 .
kfriedberger
added a commit
that referenced
this issue
Mar 8, 2025
This is a first step for #392 . The situation is also reported to Ostrich in uuverifiers/ostrich#95 .
kfriedberger
added a commit
that referenced
this issue
Mar 8, 2025
This is a first step for #392 . The situation is also reported to Ostrich in uuverifiers/ostrich#95 .
kfriedberger
added a commit
that referenced
this issue
Mar 8, 2025
This is a first step for #392 . The situation is also reported to Ostrich in uuverifiers/ostrich#95 .
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running tests, such as in this case, some of the tests seem to print warnings like the following:
Unexpected logic for quantifier elimination ALL
WARNING: optimization with quantified constraints is not supported
I am not sure how to interpret this, does this indicate a bug?
Anyway, given that these strings do not appear in the source of JavaSMT, I assume that this outputs will also appear in certain situations during regular usage of JavaSMT (outside of tests). However, JavaSMT and the solvers are libraries, they should never write to stdout or stderr unless explicitly told so by the calling application. Any output is likely to mess up the desired output of the application. Libraries should use logging, or, if the message indicate bugs, communicate this via exceptions.
The text was updated successfully, but these errors were encountered: