Test error #36
Comments
|
Maybe I should be running the release-0.5 branch of Julia? Currently on the tagged v0.5.0 |
|
Oh I forgot that we are using a patched Julia on cannon. I'll replicate the patch and see if that fixes it. |
|
Hmm I'm still getting the same error when I run the latest "release-0.5" branch with the patch that we have on cannon now |
|
Actually I'm getting the same error on cannon too, and it was also triggered by the latest Travis build |
|
I haven't run registration for a while. I can try a test run tonight to see
if I can replicate the error.
Best,
Jerry
…On Feb 21, 2017 4:59 PM, "Cody Greer" ***@***.***> wrote:
Actually I'm getting the same error on cannon too. Has anyone else ran
into this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMvfFW68bo2_pPaoYtuRL8iVO3Z2YoEWks5re2xUgaJpZM4MH6nL>
.
|
|
If I use the version of |
|
I will check that out. Do you think we should merge that version into
master? Trying to make sure I can run it on other machines.
…On Feb 21, 2017 5:33 PM, "Tim Holy" ***@***.***> wrote:
If I use the version of BlockRegistration that's installed at
/usr/local/julia/julia-0.5/usr/share/julia/site/v0.5/
BlockRegistration/test (which is what you use if you *don't* have it
installed in your own private v0.5 directory), then the
register_mismatch.jl test passes for me. Looks like I missed a depwarn or
two in RegisterMismatchCuda, though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE78hBg7B-lyMBHY5u_g1Rbh64YvipByks5re3QtgaJpZM4MH6nL>
.
|
|
I think it is, but it's worth investigating further. I'm in the middle of fixing the depwarn and I'm using that version (I shouldn't do that), so right now it's ahead of master. |
|
I think the Travis failure on the AffineTransforms fix PR suggests it's not
in master, right?
…On Feb 21, 2017 5:41 PM, "Tim Holy" ***@***.***> wrote:
I think it is, but it's worth investigating further. I'm in the middle of
fixing the depwarn and I'm using that version (I shouldn't do that), so
right now it's ahead of master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#36 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE78hKqzVJEToKLUoxlx5U4XidW89b_5ks5re3Y_gaJpZM4MH6nL>
.
|
|
Travis is running 0.5.0. |
|
Very strange, I just got the same error when using the packages installed in Also in order to use those packages I had to run julia as super user, or else I get an error when trying to use precompiled stuff: |
|
Here's my |
|
So this is really bizarre. I just noticed that I get the above error when running |
|
Ah, that's interesting. I think function getindex{T}(v::UnitRange{T}, i::Integer)
convert(T, first(v) + i - 1)
endwhich is just a simple computation, not a memory-access. Looking at the line corresponding to the error, it's in a part of the code that is deliberately violating bounds. In block registration, of our blocks are of the same size, and each block is centered on a grid position; the grid extends all the way to the corners of the image (this makes fine-scale interpolation for warping much cleaner, we don't have to extrapolate In other words, the error you're getting does not appear to be anything to worry about: it's how the code is supposed to work. Perhaps we should rewrite that code so you can use |
|
I see, that all makes sense, thanks! So I guess it's conventional that Travis calls the I don't think I have time at the moment to update the code for |
No, it usually runs Yes, let's leave this open. |
I'm getting this test error in Julia 0.5. I also tried starting from a fresh empty package directory and still get the same error.
The text was updated successfully, but these errors were encountered: