Path: csiph.com!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!news.szaf.org!news.unit0.net!newsfeed.CARNet.hr!news.spin.it!bofh.it!news.nic.it!robomod From: Andreas Tille Newsgroups: linux.debian.maint.python,linux.debian.devel.release Subject: Re: python-scipy: autopkgtest fails (Re: bug#919929) Date: Thu, 07 Mar 2019 09:10:02 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Mar 7 08:03:20 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.98 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -3.5 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) X-Mailing-List: archive/latest/16810 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20190307080302.zc6q5ljr6vyd2yqf@an3as.eu Approved: robomod@news.nic.it Lines: 27 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org, jtaylor.debian@googlemail.com, debian-release@lists.debian.org X-Original-Date: Thu, 7 Mar 2019 09:03:02 +0100 X-Original-Message-ID: <20190307080302.zc6q5ljr6vyd2yqf@an3as.eu> X-Original-References: <3e555bf95e5228d291a7fe94beaa4ada@emerall.com> Xref: csiph.com linux.debian.maint.python:11350 linux.debian.devel.release:84880 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. 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). Kind regards Andreas. > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919929 -- http://fam-tille.de