[PkgEval] ForwardDiff may have a testing issue on Julia 0.3 (2014-05-26) about forwarddiff.jl HOT 15 CLOSED

@IainNZ, ForwardDiff seems to be missing from the 0.3 on the package listing?

from forwarddiff.jl.

Yeah there was a bug in Julia master last night (JuliaLang/julia#7067) so all packages that failed last night on 0.3 were dropped (I actually did have a try catch there, but was catching what I expected, not an UndefVarError!)

from forwarddiff.jl.

A quick question about the automatically-generated issues; is it ok if I leave them open and deal with them after a few months following Julia's release cycle? Julia's base changes with a pace that requires a time commitment on my part that I am unable time-wise to meet on a weekly basis for all 5-6 packages I have added to metadata, so if you feel happy with it, I can look into these issues once the next Julia version comes out officially (or earlier if I find the chance).

from forwarddiff.jl.

@scidom Right now ForwardDiff is broken on the latest stable release of Julia, which is the one that most users will choose by default. I don't think it's okay to leave a package in a broken state for that long. If you'd prefer not to support 0.2, then METADATA should be updated so that the package can't be installed on 0.2

from forwarddiff.jl.

Totally up to you!

from forwarddiff.jl.

I agree with you that it can cause trouble if the package remains broken for too long, will do my best to get it done soon. I will have a look at the issue over the weekend and if it is an easy quick fix, I will make sure I push the change to the package and metadata so that it is not broken. If I turn to be too slow, I won't feel bad @mlubin if you would prefer that I remove some of my packages from metadata so that I don't cause trouble to the Julia package housekeeping.

from forwarddiff.jl.

They definitely should not be removed from Metadata, as this causes no end
of problems. However, you can change the requires file so that only working
versions will be installed.

On Thursday, June 5, 2014, Theodore Papamarkou [email protected]
wrote:

I agree with you that it can cause trouble if the package remains broken
for too long, will do my best to get it done soon. I will have a look at
the issue over the weekend and if it is an easy quick fix, I will make sure
I push the change to the package and metadata so that it is not broken. If
I turn to be too slow, I won't feel bad @mlubin
https://github.com/mlubin if you would prefer that I remove some of my
packages from metadata so that I don't cause trouble to the Julia package
housekeeping.

—
Reply to this email directly or view it on GitHub
#15 (comment)
.

from forwarddiff.jl.

Yes, that's a good idea @kmsquire. I wanted to ask, how do I state in the require file that only version 0.3 is supported? I am not yet so familiar with this. I will try to update the package on Saturday as it is in my best interest to make sure it runs properly...

from forwarddiff.jl.

Hi @IainNZ, 2 questions:

1. I just updated my Julia to the latest commit and ran the tests in ForwardDiff without getting any errors. What error did you get, do you still get it?
2. How do I specify in REQUIRE that the package is only compatible with Julia v0.3?

from forwarddiff.jl.

All right, I found out how to update REQUIRE to state that only Julia v0.3 is supported. v0.3 is already in pre-release state so there is little point in putting (non-existing) time to support the older version 0.2. I checked the package and it works perfectly fine with v0.3, and updated METADATA, so I will close now this issue (drop ForwardDiff from v0.2 METADATA if you wish @IainNZ but apparently keep it in v0.3 METADATA).

from forwarddiff.jl.

It looks like this is mostly resolved. It may be worthwhile to just remove versions 0.0.0 and 0.0.1 from METADATA so that the package isn't installable on Julia 0.2. I can go ahead and do this if you like, @scidom.

from forwarddiff.jl.

Yes, @mlubin, I agree with your suggestion, go ahead with this change in METADATA.

from forwarddiff.jl.

Done. I've given you admin access to JuliaDiff to transfer over DualNumbers and ForwardDiff.

from forwarddiff.jl.

Great, thanks @mlubin. I transferred ownership of DualNumbers and ForwardDiff to JuliaDiff. I find this pleasing - although it seems at first very inconsequential to collect the packages under the umbrella of an organization, it is an excellent way of getting organized and teaming up. I am looking forward to all co-developers joining us with their autodiff packages in JuliaDiff.

from forwarddiff.jl.

Nice. It is oddly effective to do this.

from forwarddiff.jl.