On 24 January 2017 at 07:26, Andreas Tille <andr...@an3as.eu> wrote: > Hi Gregor, > > On Mon, Jan 23, 2017 at 11:45:29PM +0100, gregor herrmann wrote: >> >> The tests fail for me as well, in a chroot with networking firewalled >> off. >> >> The errors are slightly different, probably because I have http_proxy >> set: >> >> http error : Operation in progress >> XML::Simple called at >> /build/libbio-eutilities-perl-1.75/blib/lib/Bio/Tools/EUtilities.pm line 140. >> # Looks like your test exited with 255 before it could output anything. >> t/egquery.t ................. >> 1..18 >> Dubious, test returned 255 (wstat 65280, 0xff00) >> Failed 18/18 subtests >> >> etc. for all t/e*.t tests >> >> /* >> With http_proxy unset I get: > > Thanks for verifying this. > >> Anyway, it's quite clear that the tests try to access the internet >> which is forbidden by Debian policy (regardless of the fact if the >> fail gracefully or not), so they have to be skipped. >> >> Andreas, you already know the trick with debian/tests/pkg-perl/smoke-skip >> and using the file in debian/rules as well to disable tests during >> build + autopkgtest. If you don't run okg-perl-autopkgtests, you can >> use: > > Yes, I know. I simply have forwarded the issue upstream since the RFP > came from upstream and I considered it more sensible if they provide > some means to exclude http access directly in their code. > >> Of course an upstream fix, e.g. skipping tests if >> $ENV{NETWORK_TESTING} is not set etc., would be nicer. > > Exactly. :-)
I will fix this upstream. I am learning what I can about debian packaging at the moment (with pkg-perl) by trying to release some packages that are needed by bioperl developers (bug #852467). I am hoping that allow me to follow this better. > >> (Hm, is this the package that was discussed on #debian-perl on IRC >> earlier yesterday? :)) > > May be - I'm usually not on IRC ... > Yes, this is that package. I asked there about what was pkg-perl preferred method to handle network tests [1]. Carnë [1] https://lists.debian.org/debian-med/2017/01/msg00114.html