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

Don’t use internal JuMP fields #6

Closed
ericphanson opened this issue Sep 6, 2019 · 2 comments
Closed

Don’t use internal JuMP fields #6

ericphanson opened this issue Sep 6, 2019 · 2 comments

Comments

@ericphanson
Copy link
Owner

@info "Final problem has $(length(model.variable_to_zero_one)) binary variables, $(num_constraints(model, GenericAffExpr{Float64,VariableRef}, MOI.LessThan{Float64})) inequality constraints, and $(num_constraints(model, GenericAffExpr{Float64,VariableRef}, MOI.EqualTo{Float64})) equality constraints."

This causes exceptions on Travis (https://travis-ci.com/ericphanson/TravelingSalesmanExact.jl), although on Julia 1.0 at least, they don’t cause test failures for some reason. I should check back once the rest of the tests complete.

I should add compat to JuMP too.

@ericphanson
Copy link
Owner Author

ericphanson commented Sep 6, 2019

I don’t think this is why PkgEval failed though (JuliaLang/julia#32973 (comment)). It looks like tests timeout on 1.2+. This might be due to type inference regressions, since MOI had similar problems on 1.2.

Edit: as noted here JuliaLang/julia#32973 (comment)

@ericphanson
Copy link
Owner Author

I made a separate issue to track the inference problems: #7.

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

1 participant