-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 failures on Debian if built with bottleneck #1208
Comments
Thanks for the report. My guess is that this is an issue with the bottleneck build -- the large float values (e.g., 1e+248) in the final tests suggest some sort of overflow and/or memory corruption. The values summed in these tests are random numbers between 0 and 1. Unfortunately, I can't reduce this locally using the conda build of bottleneck 1.2.0 on OS X, and our build on Travis-CI (using Ubuntu and conda) is also succeeding. Do you have any more specific details that describe your test setup, other than using the pre-build bottleneck 1.2.0 package? If my hypothesis is correct, this test on bottleneck might trigger a test failure in the ubuntu build process (but it passed in bottleneck's tests on TravisCI): |
Thanks, I'll iterate with the Debian maintainer of bottleneck. |
It turned out to be a bug in numpy 1.12.0, fixed in 1.12.1, which made |
Were you able to verify that the xarray tests pass after the numpy fix? |
We'd need to wait for numpy-1.12.1 to be absolutely sure. I don't have time to deploy a dev version of numpy to test. |
OK, thanks for looking into this!
…On Wed, Jan 18, 2017 at 10:36 AM, Ghislain Antony Vaillant < ***@***.***> wrote:
We'd need to wait for numpy-1.12.1 to be absolutely sure. I don't have
time to deploy a dev version of numpy to test.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1208 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABKS1qvrlv_WzrX9rpoAD5zPY58KNJEnks5rTlu2gaJpZM4LkFPn>
.
|
Re-opening. Debian now has a version of Numpy with the fix which broke
|
I can confirm that - I have the same problems on my pip virtualenv on linux mint (I tried to reproduce it on travis without success) |
@ghisvail Thanks for your diligence on this. @fmaussion If you can turn one of these into a test case for bottleneck to report upstream that would be super helpful. I would probably start with |
@shoyer there is something very weird going on. See the following example: import numpy as np
import bottleneck as bn
import xarray as xr
da = xr.DataArray(np.ones((10, 20)).astype(np.int), dims=['x', 'y'],
coords={'abc':('y', np.array(['a'] * 9 + ['c'] + ['b'] * 10))})
np.testing.assert_allclose(np.sum(da[:, 9:10]), bn.nansum(da[:, 9:10])) # this will allways work
np.testing.assert_allclose(da.groupby('abc').reduce(np.sum), da.groupby('abc').sum()) # this won't This will work with bottleneck installed. Now change the
So the new operation is applied only to the first element of the grouped selection, and I didn't manage to us bottleneck only to replicate this (since the first assertion always passes). Before I dig into this I'd like to have your opinion on this: any idea on what could go wrong here? |
@shoyer nevermind, I found the bug: pydata/bottleneck#161 Quite a tricky one indeed ;-) |
the tests now pass with bottleneck master. |
@fmaussion thanks for puzzling this one out! @ghisvail thanks for the report! |
I added a PR in order to allow a dev version of bottleneck to be used, too: #1235 |
On my attempt to package
xarray
for Debian, I encountered the following issue whereby the package build process (which sequentially runs build, test, install for all supported Python versions) would succeed if thebottleneck
build dependency is omitted, but fail at the test stage otherwise. The version ofbottleneck
currently available in Debian is1.2.0
. The log from pytest is pasted below:The text was updated successfully, but these errors were encountered: