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

Test failure only on first run (triggered by gc?) #151

Closed
Cody-G opened this issue Aug 25, 2018 · 1 comment
Closed

Test failure only on first run (triggered by gc?) #151

Cody-G opened this issue Aug 25, 2018 · 1 comment

Comments

@Cody-G
Copy link
Contributor

Cody-G commented Aug 25, 2018

When I run tests just after installing ImageView on Julia 0.6 I get this error:

julia> include("runtests.jl")
Test Summary: | Pass  Total
contrast GUI  |    1      1
Error encountered while loading "/home/cody/Desktop/jpacks3/v0.6/TestImages/images/cameraman.tif".
Fatal error:
Library "ImageMagick" is not installed but is recommended as a library to load format: ".tif"
Should we install "ImageMagick" for you? (y/n):
y
INFO: Start installing ImageMagick...
INFO: Installing ImageMagick v0.5.2
INFO: Building FFTW
INFO: Building SpecialFunctions
INFO: Building ImageMagick
INFO: Package database updated
ERROR: LoadError: LoadError: MethodError: no method matching getindex(::Void, ::UnitRange{Int64}, ::UnitRange{Int64})
Stacktrace:
 [1] include_from_node1(::String) at ./loading.jl:576
 [2] include(::String) at ./sysimg.jl:14
 [3] include_from_node1(::String) at ./loading.jl:576
 [4] include(::String) at ./sysimg.jl:14
while loading /home/cody/Desktop/jpacks3/v0.6/ImageView/test/scalesigned.jl, in expression starting on line 16
while loading /home/cody/Desktop/jpacks3/v0.6/ImageView/test/runtests.jl, in expression starting on line 3

If I run the tests again they pass. The only way I've found to trigger the error again is to uninstall ImageMagick, close julia, reopen julia, and run the tests again. See also discussion in #145

Also note the line number in scalesigned.jl shown in the stacktrace is 16 for me because I tried adding gc() statements to force the error. The line number on master is 6.

@timholy
Copy link
Member

timholy commented Aug 26, 2018

Tests do not fail on master with 0.6, see #152. I can't get it to fail locally either.

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

2 participants