-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: test_read_pickles_0_10_1 and test_read_pickles_0_11_0 failures on sparc #3894
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
Comments
is there a sparc machine on vagrant so I can build this? |
@yarikoptic let me know if you are still having problems...thanks |
unfortunately KnownFailureTest is "no good" as is -- it is signaled as the error by nose
on a good side -- all other failures I have reported for sparc before -- are "gone" now with v0.11.0-529-gcca1b7e |
is there a way to make this pass |
http://mail.scipy.org/pipermail/numpy-discussion/2010-October/053186.html apparently known failure is a nose plugin loaded by numpy; I'll just skip these then unless you tell me otherwise.... |
yeah -- sorry for the confusion -- I have forgotten that it requires a nose plugin and not just magically works ;) indeed mandating loading of a nose plugin might be too much - skip should be enough |
np...had never used knowntestfailure (which is a good idea!) and didn't know if its 'standard' in nose, guess not (though should be!) |
yes -- it is not standard -- grows out from numpy (used in ipython etc)
Yaroslav O. Halchenko, Ph.D. |
all fixed up...thanks! |
was happening with 0.11 and now with v0.11.0-492-gb204e14:
The text was updated successfully, but these errors were encountered: