-
Notifications
You must be signed in to change notification settings - Fork 17
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
Fix printing in JuMP v1.11.1 #314
Conversation
Codecov Report
@@ Coverage Diff @@
## master #314 +/- ##
=======================================
Coverage 99.77% 99.77%
=======================================
Files 36 36
Lines 7099 7099
=======================================
Hits 7083 7083
Misses 16 16 |
The remaining errors all stem from InfiniteOpt.jl/test/point_variables.jl Lines 350 to 357 in a66bbde
which causes the subsequent checks to fail since a variable is unexpected added to the model at first. This test is intended to trigger the JuMP.check_belongs_to_model here:InfiniteOpt.jl/src/point_variables.jl Lines 423 to 432 in a66bbde
I am not quite sure why this is happening, but I will have some more time later to investigate. |
That seems to have fixed the v1.9 issue, now the tests fail as expected because of the printing. |
So I guess the question is: are you okay if we release jump-dev/JuMP.jl#3350? |
Go ahead, no worries |
Requires #316 for 1.9 tests to pass |
Merging now that julia 1.6 and docs pass the testing |
The upcoming JuMP 1.11.1 tweaks how we do printing. I'm not really sure if this is a "breaking" change or not, because it affects only the tests of InfiniteOpt, and the exact string that is printed isn't part of the API contract.
What's weird is that I couldn't reproduce the failures: jump-dev/JuMP.jl#3350 (comment)