Repository navigation
Numpy master segfaults in Scipy testsuite #8671
Description
Current numpy (2017-02-23, f24da28) crashes in Scipy test suite.
Observed on travis, and repro locally. Crashes at
$ gdb --args python runtests.py -g -t scipy/signal/tests/test_spectral.py:TestSTFT.test_permute_axes
Program received signal SIGSEGV, Segmentation fault.
0x00007fffedea4671 in PyArray_Transpose (ap=0x7fffd9244cb0, permute=0x7fffffff9b30) at numpy/core/src/multiarray/shape.c:711
711 if (reverse_permutation[axis] != -1) {
(gdb) bt
#0 0x00007fffedea4671 in PyArray_Transpose (ap=0x7fffd9244cb0, permute=0x7fffffff9b30) at numpy/core/src/multiarray/shape.c:711
#1 0x00007fffede6b5db in array_transpose (self=0x7fffd9244cb0, args=0x7fffd97a0610) at numpy/core/src/multiarray/methods.c:1956
#2 0x00007ffff7adb7a1 in PyEval_EvalFrameEx () from /lib64/libpython2.7.so.1.0
...
Result from git bisect:
564b7cb is the first bad commit
Activity
eric-wieser commentedon Feb 23, 2017
Fixed in #8672, hopefully
pv commentedon Feb 23, 2017
rgommers commentedon Feb 23, 2017
These are the only ones (in
travis-test.sh):eric-wieser commentedon Feb 23, 2017
Is there any way to make travis at least report other warnings? I've only ever seen them when there's also a failure
pv commentedon Feb 23, 2017
pv commentedon Feb 23, 2017
eric-wieser commentedon Feb 23, 2017
I think the issue is that travis is discarding the build stdout/stderr when it succeeds - I've seen warnings be emitted in the past. They just get emitted into nothingness... Maybe I'm just missing something in the travis UI.
rgommers commentedon Feb 23, 2017
It's not TravisCI, it's pip.
pip install .is completely silent. Changing it topip install . -vwill show the build log.rgommers commentedon Feb 23, 2017
Possible but nontrivial I suspect.
Adding a limited set of explicit warnings to
werrorsthat doesn't conflict with_configtestand making the build log visible for the rest may be a better work/reward trade-off.juliantaylor commentedon Feb 23, 2017
we do error out on warnings, the issue is only on our 32 bit build and on 32 bit intp == int so we miss warnings about this.
We can probably add the warning checker to all builds but they use much older versions of gcc so they may be less good. Besides false positives not a big issue as we still have the one build with a new gcc.
juliantaylor commentedon Feb 23, 2017
but in any case -Wincompatible-pointer-types is probably a good choice for a fatal warning on all builds.
eric-wieser commentedon Feb 28, 2017
Presumably this can be closed, since #8672 is merged, and discussion about warnings continues at #8676