On 17/03/10 at 14:39 +0100, Florian Hinzmann wrote: > > On Wed, 17 Mar 2010 14:13:01 +0100 > Florian Hinzmann <f.hinzm...@hamburg.de> wrote: > > > 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? > > Kind of P.S.: > I assumed the build daemons would both > - have online access and > - use nocheck to save cpu cycles. > > Thinking about it now, it might be good to run the tests > with the builds, especially to check them on every architecture. > > So one question remains: May I assume to have online access when > building packages. > > Maybe I find a way to skip or timeout these non-fatally. > > AMD64 build fine otherwise (including the IPv4 online test): > https://buildd.debian.org/fetch.cgi?pkg=libnet-dns-perl;ver=0.66-1;arch=ia64;stamp=1268659347
The build was not done on an official buildd. I run archive rebuilds on a regular basis on a cluster, and do that to detect a lot of FTBFS bugs. So far, failing to build because network is not available has always been considered an RC bug. -- | 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
