Path: csiph.com!weretis.net!feeder4.news.weretis.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod From: Diane Trout Newsgroups: linux.debian.maint.python Subject: Re: Python 3 Statsmodels & Pandas Date: Mon, 18 Sep 2017 07:20:02 +0200 Message-ID: References: X-Original-To: Stuart Prescott , debian-science@lists.debian.org, debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Sep 18 05:14:42 2017 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.9 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.24.5-3 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/15197 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/1505711658.1083.20.camel@ghic.org Approved: robomod@news.nic.it Lines: 34 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 17 Sep 2017 22:14:18 -0700 X-Original-Message-ID: <1505711658.1083.20.camel@ghic.org> X-Original-References: <1384861181.23137.1.camel@debiousci.pietrobattiston.it> <87a81uuzqj.fsf@wavexx.thregr.org> <1505596690.2395.27.camel@ghic.org> <3385857.0h487Vp43N@jatayu> Xref: csiph.com linux.debian.maint.python:9815 > On Saturday, 16 September 2017 14:18:10 AEST Diane Trout wrote: > > My solution was to use build-profiles to flag the test dependency > > with > > !nocheck > > this is, of course, a very elegant solution and exactly what build > profiles > are for... > > I wonder though, is it really sustainable given this problem keeps > coming up? I just did it that way because it was the least disruptive change I could make that would let me build and test the package. Also I wasn't sure how much magic was happening on the Debian build servers. > > Is it feaible to completely break this circular dependency? If it is > only > needed for tests, would be possible to disable the build-time tests > and rely In my experience I'm much more likely to to notice a build time test failure than one from the CI system. Though I did adjust my pbuilder config to fail on test failures in the autopkgtests so I already solved my own concern... What do other people think? If there are autopkgtests, should you still let dh_auto_test run tests? Diane