On 2019-03-07 19:00, Paul Gevers wrote:
Hi Drew,
On 07-03-2019 09:03, Andreas Tille wrote:
On Tue, Mar 05, 2019 at 07:01:54PM +0800, Drew Parsons wrote:
python-scipy has recently started failing all debci tests in testing
and
unstable, exacerbating the bug report in Bug#919929 [1].
The failing error is a MemoryError. But understanding the problem is
hampered by a flood of deprecation warnings, presumably triggered by
numpy
1.16. scipy 1.2 added instructions to pytest.ini to ignore the
warnings.
Bug#919929 has not yet been marked RC but I guess it's about to
happen.
Can you elaborate why you think that bug should be RC (as that isn't
clear to me from the report itself) and why you haven't marked it as
such if you think it should be?
python-scipy is currently failing all debci tests in both unstable and
testing.
I haven't marked it RC myself since I'm not 100% certain what the usual
protocol is for marking the severity of debci test failures. But as I
understood it, debci test failures is considered RC under the final
freeze which we're about to enter (but we're not quite in that deep
freeze yet).
I
propose in the first instance to apply a patch of the pytest.ini diff
between scipy 1.1 and 1.2 and see if that clears things up. I'll
commit the
patch now. Should I proceed with upload to unstable?
May be its sensible to coordinate with debian-release (list in CC) and
file a unblock request *before* uploading. I confirm that I usually
upload simple fixes and ask for unblock afterwards but you intend to
do
a version change which does not qualify as simple fix (despite I agree
with you that it is sensible).
Hi Andreas, I may not have been clear. What I mean at this point is to
upload a small patch for scipy 1.1 to ignore the deprecation warnings
(scipy 1.2 already does that).
If that doesn't help pass the debci tests then we can consider uploading
scipy 1.2 instead. But python-fluids and dipy FTBFS against scipy 1.2
(a new version of dipy is available which presumeably fixes that)
Slightly depending on the answer above, I'll unblock an upload of
python-scipy with only that change.
Certainly please do unblock if the full freeze is already in place. But
my intention was to first upload python-scipy 1.1 with a small patch,
not 1.2 just yet.
Drew