On 25/10/2013 13:19, Jonas Smedegaard wrote: > Quoting Mike Gabriel (2013-10-25 13:05:48) >> On Fr 25 Okt 2013 11:14:48 CEST, Jonas Smedegaard wrote: >>> Quoting Mike Gabriel (2013-10-25 09:11:59) >>>> On Do 24 Okt 2013 20:32:33 CEST, Jérémy Lal wrote: >>>>> On 24/10/2013 20:17, Mike Gabriel wrote: >>>>>> when I try to build nodejs from testing (0.10.20~dfsg1-1) for >>>>>> wheezy-backports, I get failures during the test runs . This >>>>>> error, however, does not occur always. Today, one of the builds >>>>>> succeeded. All other builds failed so far. >>> >>>>> That test isn't used to fail... but is probably failing because of >>>>> your particular setup: maybe a missing loopback interface, or >>>>> IPv6-only, or restrictive firewall. >>>>> Did you build it in a chroot ? >>> >>>> I disabled my local firewall setup, that did the trick. For building >>>> packages I use sbuild/schroot. >>>> >>>> Thanks for pointing at my firewall setup! >>> >>> That worries me: Does that mean Nodejs testsuite rely on network >>> access? That sounds wrong to me! > >> The testsuite does some localhost testing. I don't think that access >> to 0.0.0.0 is needed. Only a loop device is requires AFAICouldT. > >> However, I did not investigate any further. >> >> As Debian's buildd chroot's are offline when building, I guess we >> would have realized earlier, if the package requires network access... >> (then buildd builds would have failed IMHO). > > Thanks for confirming sanity :-) > > I did hope for the situation you describe, but better double-check than > blindly assume all is well :-)
Many tests actually require network. There are some DNS tests, for example. But those tests are allowed to fail. Jérémy.
Description: OpenPGP digital signature