Bug#792221: libnet-frame-device-perl: FTBFS without networking: t/04-new-default and t/05-new-target fail

[solo-debianbugs at goeswhere.com]

On Mon, Jul 13, 2015 at 01:19:29AM +0200, gregor herrmann wrote:
> > Full build log:
> > https://reproducible.debian.net/rb-pkg/unstable/amd64/libnet-frame-device-perl.html
> 
> It seems to be a bit more complicated than that.
> 
> With "USENETWORK=no" I indeed see the failures:
> ...
> # Using Test.pm version 1.26
> Dubious, test returned 101 (wstat 25856, 0x6500)
> Failed 1/1 subtests 
> Possible precedence issue with control flow operator at /tmp/buildd/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
> Net::Frame::Device: updateFromTarget: unable to get dnet
> t/05-new-target.t .... 
> 1..1
> # Running under perl version 5.020002 for linux
> # Current time local: Sun Jul 12 23:16:50 2015
> # Current time GMT:   Sun Jul 12 23:16:50 2015
> # Using Test.pm version 1.26
> Dubious, test returned 101 (wstat 25856, 0x6500)
> Failed 1/1 subtests 
> 
> 
> but only during the build, when cowbuilder drops me into a shell, a
> manual `prove --blib --verbose t/*.t' works fine.

I was manually re-testing things inside lxc (with eth0 down), and can
hit the failure even with `prove`:

% lxc-attach -n sid2
root at sid2:~# cd libnet-frame-device-perl-1.10/
root at sid2:~/libnet-frame-device-perl-1.10# ifdown eth0
[...]
root at sid2:~/libnet-frame-device-perl-1.10# prove --blib --verbose t/*.t
t/01-use.t ...........
[...]
t/04-new-default.t ... 
1..1
# Running under perl version 5.020002 for linux
# Current time local: Mon Jul 13 07:23:47 2015
# Current time GMT:   Mon Jul 13 07:23:47 2015
# Using Test.pm version 1.26
Possible precedence issue with control flow operator at /home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
Net::Frame::Device: updateFromDefault: unable to get dnet
Dubious, test returned 101 (wstat 25856, 0x6500)
Failed 1/1 subtests 
t/05-new-target.t .... 
1..1
# Running under perl version 5.020002 for linux
# Current time local: Mon Jul 13 07:23:47 2015
# Current time GMT:   Mon Jul 13 07:23:47 2015
# Using Test.pm version 1.26
Possible precedence issue with control flow operator at /home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
Net::Frame::Device: updateFromTarget: unable to get dnet
Dubious, test returned 101 (wstat 25856, 0x6500)
Failed 1/1 subtests 



Is it my imagination, or does that "unable to get dnet" message appear
in the 05 test only for me?



---

And, because I failed to send the e-mail before getting distracted, I
did some debugging:

The (apparent) error is it calling intf_get_dst('1.1.1.1') which
"retrieves the configuration for the best interface with which to
reach the specified dst.", which fails.

Indeed, I can reproduce this for 04 by blackholing 1.1.1.1 (I don't
actually know what this does, but it sounds cool):

root at sid2:~/libnet-frame-device-perl-1.10# prove --blib --verbose t/*.t >/dev/null 2>&1 && echo passed
passed
root at sid2:~/libnet-frame-device-perl-1.10# ip r add blackhole 1.1.1.1/32
root at sid2:~/libnet-frame-device-perl-1.10# prove --blib --verbose t/*.t

t/04-new-default.t ... 
1..1
[...]
Possible precedence issue with control flow operator at /home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
Net::Frame::Device: updateFromDefault: unable to get dnet
Dubious, test returned 101 (wstat 25856, 0x6500)
Failed 1/1 subtests 
t/05-new-target.t .... 
1..1
[...]
# Using Test.pm version 1.26
Possible precedence issue with control flow operator at /home/faux/libnet-frame-device-perl-1.10/blib/lib/Net/Frame/Device.pm line 63.
$VAR1 = {
          'gatewayIp' => '10.0.3.1',
[...]
root at sid2:~/libnet-frame-device-perl-1.10# ip r del 1.1.1.1


Does that help you reproduce it?  I suspect the answer is simply to disable
these tests if there isn't public connectivity (or just generally), however.