The numpy EasyBlock runs the unittests as "cd .. && %(python)s -c 'import numpy; numpy.test(verbose=2)'"
However the numpy.test function returns True/False depending on success. As that is never checked the exit code is always 0 (unless a segfault or similar occurred). See https://github.com/numpy/numpy/blob/360ba0572483457837992d711a0a00580741fc88/numpy/_pytesttester.py#L213
This means we basically run the tests but ignore any failures other than hard crashes. And with 2019b numpy I see errors in the test suite (caused by having LDFLAGS set)
I don't think this is intentional and hence should be changed.
I assume scipy has the same problem as it is similar.
The numpy EasyBlock runs the unittests as
"cd .. && %(python)s -c 'import numpy; numpy.test(verbose=2)'"However the
numpy.testfunction returns True/False depending on success. As that is never checked the exit code is always 0 (unless a segfault or similar occurred). See https://github.com/numpy/numpy/blob/360ba0572483457837992d711a0a00580741fc88/numpy/_pytesttester.py#L213This means we basically run the tests but ignore any failures other than hard crashes. And with 2019b numpy I see errors in the test suite (caused by having LDFLAGS set)
I don't think this is intentional and hence should be changed.
I assume scipy has the same problem as it is similar.