JuliaWeb
Support for precompilation with version check
Why is this failing? Does this have to do with precompilation? Doesn't appear so.
https://travis-ci.org/JuliaWeb/HTTPClient.jl/jobs/97959624
@tkelman Any ideas what's going on here?
Nope. Harsha checked it and it fails even without precompile stuff.
Regards, Pradeep
On 24-Dec-2015, at 3:33 PM, Viral B. Shah [email protected] wrote:
Why is this failing? Does this have to do with precompilation? Doesn't appear so.
https://travis-ci.org/JuliaWeb/HTTPClient.jl/jobs/97959624 https://travis-ci.org/JuliaWeb/HTTPClient.jl/jobs/97959624 @tkelman https://github.com/tkelman Any ideas what's going on here?
— Reply to this email directly or view it on GitHub https://github.com/JuliaWeb/HTTPClient.jl/pull/26#issuecomment-167080751.
What exactly is the failure locally with precompilation off? I frequently see an http code mismatch intermittent failure where a return code is 503 instead of 200, but these failures are different. I lean towards saying this package is not precompile safe.
Exact error message when precompilation is off , can be found in this gist
https://gist.github.com/bmharsha/ee7cc04d38c12ebeaa59#file-precompilation_off_metadata-md
Error message when precompilation is on can be found here
https://gist.github.com/bmharsha/ee7cc04d38c12ebeaa59#file-precompilation_on-md
That ReadOnlyMemoryError looks entirely separate and likely unrelated to precompilation.
Given the "Error executing request : Failed writing received data to disk/application" and the segfaults, I suspect this package isn't precompile-safe as currently written.
See https://travis-ci.org/JuliaWeb/HTTPClient.jl/builds/88606158, I just restarted that. Master passes, or at least passes some of the time (there's an intermittent http code mismatch failure, but I don't usually see segfaults) with precompilation off. I'll restart the PR build too, see how consistent the new failure/segfault is.