-
Notifications
You must be signed in to change notification settings - Fork 9
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
Testsuite fails in Debian unstable #23
Comments
Any news on this? |
Hi Ghislain, I'll get to it tomorrow. Thanks for the report! 2016-01-30 16:42 GMT+01:00 Ghislain Antony Vaillant <
La propagande est à la démocratie ce que la violence est à la dictature. |
Any news on that? |
I still get the I believe all relative imports listed above should be replaced by |
I am putting my last comment back, |
Linked with #24. A missing |
I've been working on it these last days. Could you please check if 0.13.12 still exhibits these failures? |
The testsuite now runs, but there are still a few things:
|
And most importantly, the testsuite fails for pretty much all architectures but I can confirm that the tests implemented in |
Most of the build errors should now be fixed in 0.13.13. I don't have a non |
Err... 0.13.14 should also fix the test failures when numexpr is not present. |
Ok, I'll refresh the packaging and report if there are still issues. Thanks for the prompt fixes. |
Still fails on 32-bit for
For the error, looks like neither For the failures, not sure what you are trying to test, so I'll let you investigate how the assertion happens to be false on 32-bit. |
The new logs are available here. Still a large range of architectures failing. |
I have fixed a good number of issues related to 32bits platforms, float128 handling and big endian platforms. Could you please rerun the testsuite using 0.13.13.post04? Thanks! |
I ran the packaging on |
Hey Pierre, I have another batch of test suite failures to report after upgrading the packaging to the latest
0.13.10
tag. This triggered an autoremoval request from Debian, since the package build cannot pass with the test failing. Could you please have a look at it? Thanks.The text was updated successfully, but these errors were encountered: