On Thu, Jan 16, 2014 at 05:19:16PM +0100, Martin Pitt wrote: > Package: mercurial > Version: 2.8.1-2 > User: autopkgtest-de...@lists.alioth.debian.org > Usertags: autopkgtest > > Hello,
Hi Martin, > mercurial's autopkgtest currently fails [1] in two different ways: > > * testsuite: > > | adt-run: & dsc0t-testsuite: - - - - - - - - - - stderr - - - - - - - - > - - > | warning: Tested with unexpected mercurial lib: > /usr/lib/python2.7/dist-packages/mercurial > | (expected /usr/bin/mercurial) > > autopkgtests must not write anything to stderr by default, so that > unexpected warnings etc. are caught. If this is expected and cannot > easily be suppressed, then you can add "Restrictions: allow-stderr" > to its control stanza, as in attached debdiff. Applied, will be in mercurial-2.9-1. Thanks! > * hgsubversion: > > In Ubuntu's CI machinery we don't have access to outside servers > like alioth. This of course does not directly affect Debian, I > mostly mentioned it to explain why I disabled that particular test > in Ubuntu in case you wonder. > > Would you accept a patch that sets up a local svn repository with > some example commits and then imports from that? This makes the > test independent of network, connectivity, or alioth problems, and > as autopkgtest is primarily meant to be a "do I have everything > required in the package" smoketest, it should suffice. I'd definitely accept it. I don't really like the current test for hgsubversion, it's just the best I could come up with. Cheers, Javi
signature.asc
Description: Digital signature