-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
Add a doctest for GLPK error handling and verbose output #20832
Comments
New commits:
|
Commit: |
comment:3
Positive review, though I personally would think it would be better to test whether there is some output rather than test for specific output, which might change whenever a new version of GLPK is installed. |
Reviewer: Matthias Koeppe |
comment:4
Replying to @mkoeppe:
How would you write the doctest then? The ellipsis |
comment:5
How about
|
comment:6
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed branch from u/jdemeyer/add_a_doctest_for_glpk_error_handling_and_verbose_output to |
The interaction between GLPK error handling and verbose output should be doctested. This would break without the custom
have_error.patch
for GLPK in Sage.CC: @kiwifb
Component: doctest coverage
Author: Jeroen Demeyer
Branch/Commit:
75e8fe2
Reviewer: Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/20832
The text was updated successfully, but these errors were encountered: