JuMP and Julia 0.7/1.0

jump

#1

Updated Oct 1: tl;dr: Thanks mostly to the persistence of @ExpandingMan, JuMP 0.18.3 was released today supporting Julia 0.6, 0.7, and 1.0. Upgrade away!

If you are using JuMP 0.18 on Julia 0.6, we do recommend upgrading now to Julia 0.7 and JuMP 0.18.3. Use Julia 0.7 to assist with updating existing code. If the code runs without deprecation warnings on Julia 0.7, it should run on Julia 1.0 (with some exceptions). Note however that not all solvers have been updated for Julia 1.0/0.7 yet. (We have 17 solvers under the JuliaOpt organization.) There are known issues with Cbc and Clp. Please give your favorite solver a try and report any issues that arise. Pull requests are even better :slight_smile:

As a reminder, JuMP 0.18.x is the last release to support the MathProgBase API. We will continue to support JuMP 0.18.x on Julia 0.6/0.7/1.0, but most developer effort is focused on the next release of JuMP which supports the MathOptInterface (MOI) API. JuMP 0.19 may require Julia 1.0 (this isn’t decided yet). Expect an alpha tag of JuMP 0.19 with accompanying announcement soon.


using JuMP - LoadError: UndefVarError: start not defined
Error building Cbc
#2

#3

Thanks for the update. Please note that the current JuMP master is really upsetting the package manager because the upper limits on the dependencies are causing “unjustifiable requirements”. Any chance these can be removed (doing so was the only way I was able to get it running), or do you guys have some procedure for dealing with it?


#4

JuMP master is passing on Travis with the upper limits as is. I can’t say what’s causing your issue.


#5

Sorry, I just tried building on another machine and am not having the issue, so I think my problem must have been a package I had on dev, even though I thought I had freed all of the JuMP dependencies. If it’s a common issue I have when developing multiple packages I’ll post back here with how to resolve. Thanks.

Update: Ok, in case this is helpful to anyone else, I think I have figured out something that has been causing me a great deal of confusion with the new package manager and which I think was causing this issue. With the new package manager, if you have a package in dev, once you do a pull you still need to do dev PackageName in the package manager again, otherwise Pkg will not update its metadata.


#6

Any estimates of when JuMP will be released for Julia 1.0? :slight_smile: Looking forward to it.
I still have Julia 0.6 because of this.


#7

For JuMP 0.18, we’ve been having some trouble with some anomalous segfaults on Julia 0.6 on travis, which have thus far been impossible to reproduce locally. (So far they have never appeared at all on Julia 0.7 or later, so they’re probably nothing to worry about if you’re on 1.0.) This has made testing the last few PR’s rather horrible.

If you want to check our progress, feel free to use the release-0.18 branch of JuMP which should work fine for most things on 1.0. Be warned however: all the same caveats apply to this as apply to 0.19 until they are tagged.


#8

Not true, we have plenty of segfaults crashes on 1.0:
https://ci.appveyor.com/project/JuliaOpt/jump-jl/build/1.0.1011/job/074p8h5f676bajc7#L184 (windows/1.0)
https://travis-ci.org/JuliaOpt/JuMP.jl/jobs/433523257#L307 (mac/1.0)
https://travis-ci.org/JuliaOpt/JuMP.jl/jobs/433523251#L864 (linux/1.0)

(Context: https://github.com/JuliaOpt/JuMP.jl/pull/1498)


#9

Thanks for the links. To be precise, these are illegal instructions, not segfaults.


#10

These look like a distinct problem, though I don’t have the expertise to know for sure. I certainly haven’t seen this before that most recent PR, do we know if this is a new issue as of the GLPK PR, or were they lurking around before and I just missed them?


#11

#12

Awesome!