On 17/03/10 at 14:13 +0100, Florian Hinzmann wrote:
> Hello!
> 
> 
> On Wed, 17 Mar 2010 13:39:06 +0100
> Lucas Nussbaum <lu...@lucas-nussbaum.net> wrote:
> 
> > Relevant part:
> > > make[1]: Entering directory 
> > > `/build/user-libnet-dns-perl_0.66-1-amd64-jA4Owr/libnet-dns-perl-0.66'
> > > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" 
> > > "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> > > # 
> > > # These tests were ran with:
> > > # Net::DNS::VERSION:               0.66
> > > # set environment variable NET_DNS_DEBUG to get all versions
> > > t/00-load.t ................ ok
> > > t/00-pod.t ................. skipped: Test::Pod v0.95 required for 
> > > testing POD
> > > t/00-version.t ............. ok
> > > # 
> > > # 
> > > # Executing heuristic to see if have unlimited view of the Internet
> > > # If the heuristic fails this could have various reasons probably having
> > > # nothing to do with bugs in Net::DNS
> > > # 
> > > # 
> > > t/001-connection-checks.t .. ok
> 
> > > [...]
> 
> 
> > > Servers [193.0.14.129 198.41.0.4 ] did not give answers at 
> > > /build/user-libnet-dns-perl_0.66-1-amd64-jA4Owr/libnet-dns-perl-0.66/blib/lib/Net/DNS/Resolver/Recurse.pm
> > >  line 112.
> > > Servers [198.41.0.4 192.58.128.30 192.112.36.4 202.12.27.33 192.5.5.241 
> > > 128.63.2.53 192.36.148.17 192.33.4.12 192.228.79.201 199.7.83.42 
> > > 128.8.10.90 193.0.14.129 192.203.230.10 ] did not give answers at 
> > > /build/user-libnet-dns-perl_0.66-1-amd64-jA4Owr/libnet-dns-perl-0.66/blib/lib/Net/DNS/Resolver/Recurse.pm
> > >  line 112.
> 
> > > [...]
> 
> > > make[1]: *** [test_dynamic] Terminated
> > > E: Caught signal 'Terminated': terminating immediately
> > > make: *** [build-stamp] Terminated
> > > Build killed with signal TERM after 60 minutes of inactivity
> > > ────────────────────────────────────────────────────────────────────────────────
> > > Build finished at 20100317-0159
> 
> 
> The test suite does include online checks. I had the whole test suite disabled
> within debian/rules before as to go easy on our build daemons.
> 
> Now with DEB_BUILD_OPTIONS=nocheck I did enable them, but
> skip if nocheck was given.
> 
> 
> Do we have a policy or best practice on what to do about tests in
> general and online tests in particular with respect to build daemons?

Yes: it is a good idea to make online tests errors non-fatal, or disable
the online tests completely. The risk is that, in 2 years, you want to
do a security update, and then the tests start failing because they
depend on an external server.
-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to