Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Ben Finney Newsgroups: linux.debian.maint.python Subject: Re: Help for Python mock test suite needed Date: Sun, 14 Aug 2016 02:50:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun Aug 14 00:40:14 2016 Old-Return-Path: X-Amavis-Spam-Status: No, score=-4.206 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MEDS2=2, RDNS_NONE=0.793] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 X-Injected-Via-Gmane: http://gmane.org/ Lines: 37 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) X-Public-Key-ID: 0xAC128405 X-Public-Key-Fingerprint: 517C F14B B2F3 98B0 CB35 4855 B8B2 4C06 AC12 8405 X-Public-Key-URL: http://www.benfinney.id.au/contact/bfinney-pubkey.asc X-Post-From: Ben Finney Cancel-Lock: sha1:YsgqBjOts8E1HCwWccN3Buptyg4= X-Mailing-List: archive/latest/14103 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/85oa4wyyie.fsf@benfinney.id.au Approved: robomod@news.nic.it Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Sun, 14 Aug 2016 10:39:37 +1000 X-Original-Message-ID: <85oa4wyyie.fsf@benfinney.id.au> X-Original-References: <20160809213240.GA22935@an3as.eu> <20160813064034.GA22254@an3as.eu> <2201782.mV6MicLdnE@kitterma-e6430> <20160813222229.GI22254@an3as.eu> X-Original-X-Complaints-To: usenet@blaine.gmane.org Xref: csiph.com linux.debian.maint.python:8762 Andreas Tille writes: > Hi Scott, > > On Sat, Aug 13, 2016 at 12:41:42PM -0400, Scott Kitterman wrote: > > > > > > > > Any more complete hint from a possibly bowtie2 user would be helpful > > > > > > > > Andreas. > > > > > > > > [1] svn://anonscm.debian.org/debian-med/trunk/packages/srst2/trunk/ > > > > A link to a build log showing the test failure might be helpful. > > There is no such link. You could make one: * Build the package using Sbuild (you are doing this already to ensure the build works cleanly, right?) * Take the output from the Sbuild run. * Paste that file on . * Reply here with the link to that complete build log. This is an essential tool of collaborating on packaging: Ensure your builds are initiated in their entirety with a single command, and all output is captured for later inspect. This is why it's important to use Sbuild or something equivalent. -- \ “Science embraces facts and debates opinion; religion embraces | `\ opinion and debates the facts.” —Tom Heehler, _The Well-Spoken | _o__) Thesaurus_ | Ben Finney