Package: python-scipy Version: 1.1.0-4 Followup-For: Bug #919929 Curiously, only python2 is affected now. Same sympton, MemoryError, now in TestInt32Overflow.test_matvecs and TestInt32Overflow.test_dia_matvec.
Assuming the MemoryError is again triggered by excessive warnings, the warning generating the most messages now is RemovedInPytest4Warning: MarkInfo objects are deprecated as they contain merged marks which are hard to deal with correctly. Please use node.get_closest_marker(name) or node.iter_markers(name). Docs: https://docs.pytest.org/en/latest/mark.html#updating-code Actually I think the problem is in python-pytest, not in python-scipy anyway. The file references are /usr/lib/python2.7/dist-packages/_pytest/mark/evaluate.py:82 /usr/lib/python2.7/dist-packages/_pytest/mark/evaluate.py:103 /usr/lib/python2.7/dist-packages/_pytest/nodes.py:296 /usr/lib/python2.7/dist-packages/_pytest/skipping.py:84 etc pytest is due for an upgrade from 3.10.1 to 4.4.0. I'm inclined not to be troubled by this, not as far as scipy goes, anyway. I expect it will clear out with natural upgrades post-buster. CI testing isn't performed in buster, is it? If it's important to get a clean buster CI test then those 2 tests could be switched off in python2 if desired. Drew