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

WIP: TEST: relaxed precision #538

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
2 participants
@Garyfallidis
Member

Garyfallidis commented Jan 3, 2015

Relaxed test decimal precision after bot error reported here
http://nipy.bic.berkeley.edu/builders/dipy-py3.3-pip/builds/138/steps/shell_4/logs/stdio

@arokem

This comment has been minimized.

Member

arokem commented Jan 3, 2015

This will not help here. The problem is not one of precision. The array shapes are different!

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Jan 3, 2015

But the bot says : Arrays are not almost equal to 6 decimals

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Jan 3, 2015

Oh yeah. You are correct. There is a shape mismatch.

@Garyfallidis Garyfallidis changed the title from TEST: relaxed precision to WIP: TEST: relaxed precision Jan 3, 2015

@arokem

This comment has been minimized.

Member

arokem commented Jan 3, 2015

Weird, huh? It's like move_streamlines sometimes drops a node, or EuDX
produces different numbers of nodes, depending on the affine used.

On Sat, Jan 3, 2015 at 12:33 PM, Eleftherios Garyfallidis <
notifications@github.com> wrote:

Oh yeah. You are correct. There is a shape mismatch.


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

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Jan 3, 2015

Which both sound impossible!

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Jan 3, 2015

And we don't see this happening in other buildbots. This is strange...

@arokem

This comment has been minimized.

Member

arokem commented Jan 3, 2015

Agreed - and this was triggered by commits entirely unrelated to this piece of code. I suspect some foul play - anything from setuptools, through pip, to the spirit of Lee Harvey Oswald.

@arokem

This comment has been minimized.

Member

arokem commented Jan 3, 2015

Also, why is that bot not pulling the most recent version of the code? It seems that even this morning it was still pulling a version a few days old.

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Jan 3, 2015

Look here at shell 3
http://nipy.bic.berkeley.edu/builders/dipy-py3.3-pip/builds/139/steps/shell_3/logs/stdio
Why is it picking up dipy 0.7.1? And not dipy 0.8.0.dev or something?

@Garyfallidis

This comment has been minimized.

Member

Garyfallidis commented Jan 4, 2015

Closing this PR as we saw that the error appears only with old OSX versions (for example 0.6 or 0.8) and old python 3 versions. Specifically only with Python 3.3 not with Python 3.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment