-
Notifications
You must be signed in to change notification settings - Fork 48
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
numpy/scipy test suite failures on aarch64/neoverse_v1
(SciPy-bundle)
#318
Comments
As discussed with @laraPPr, next steps before looking into reporting this upstream are:
|
While trying to rerun the tests (numpy.fft.test(verbose=3) and numpy.polynomial.test(verbose=3)) on the neoverse_v1 aws clusters ( c7g.2xlarge and c7g.4xlarge). I found that EESSI was using the neoverse_n1 installs. So it will be difficult to rerun the failing tests of the numpy that is now in place for neoverse_v1 architectures.
|
Hmm, it's worth figuring out why You can bypass what archspec thinks is the most suited software substack by setting
|
Where should I open that issue? |
numpy.fft.test(verbose=3)
c |
numpy.polynomial.test(verbose=3)
|
Issue on problems with CPU detection should go here in |
aarch64/neoverse_v1
(SciPy-bundle)
When extending the list of known issues with more info (see PR #340), I noticed that there are also 2 failing tests in the
and 55 failing tests in
|
With There are also failing tests for
|
With
edit: this should be put in context though, since total tests also went up from 35441 (scipy 1.8.1) to 49043 (scipy 1.10.1) |
Some more updates here: For
For |
{2023.06}[foss/2023a,foss/2023b] ignore fakeroot and do not remove packages & rebuild GCCcore 12.3.0 / 13.2.0
For
That's in line with what we've seen for |
We're seeing a number of failing tests in the numpy test suite on ARM neoverse_v1 in:
For now, we've ignored the failure of the following tests, but we'll need to investigate this issue in more detail. Will the test failures of SciPy-bundle pop up in more installs on ARM neoverse_v1 where we also increased the number of accepted test failures for OpenBlas? Or will this result in more problems when installing other software dependant on numpy?
See also:
It did not seem to be a problem however in:
The text was updated successfully, but these errors were encountered: