Package: python-scipy
Followup-For: Bug #919929
Should be easier than it looks: the structure is already in place in
debian/tests/python2.
Hi Drew,
On Mon, 08 Apr 2019 17:52:02 +0800 Drew Parsons wrote:
> 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.
Obviously we do *want* to use autopkgtest post release in buster as
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
Package: python-scipy
Followup-For: Bug #919929
debci tests are consistently passing with python-scipy/1.1.0-4
I think we can consider this bug resolved now.
Drew
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Package: python-scipy
Followup-For: Bug #919929
Probably a simple pytest.ini diff between scipy 1.1 and 1.2 makes the
simplest patch:
--- pytest.ini.old 2019-03-05 18:36:51.532842277 +0800
+++ pytest.ini 2019-02-28 11:57:04.155637459 +0800
@@ -7,5 +7,8 @@
error
Package: python-scipy
Followup-For: Bug #919929
No, I am wrong. Tests are pytest, the junit reference is --junitxml,
indicated test reports are in junit format.
The question then, is why is the instruction in pytest.ini to ignore
deprecation warnings not being honoured?
Ah I see it. I'm
Package: python-scipy
Followup-For: Bug #919929
Note PendingDeprecationWarning is set to be ignored in pytest.ini.
The problem is that the tests in debian/tests do not use pytest...
Package: python-scipy
Followup-For: Bug #919929
Something weird going on with the scipy tests. There's a clue in this
bug report already: "MemoryError".
Fails are now consistent since 25/2/2019. The funny thing is, even
when I try to access the test log for the last successful
8 matches
Mail list logo
