NFD

The compilation and tests for NFD and ndn-tools all ran successfully. However, I'm getting some strange FaceUri canonization errors in the ndn-cxx unit tests, perhaps related to what we experienced when deploying 17.04 (#4095).

Running 1008 test cases...
../tests/unit-tests/interest.t.cpp(267): error: in "TestInterest/MatchesInterest": check interest.matchesInterest(other) == false has failed [true != false]
../tests/unit-tests/net/face-uri.t.cpp(88): error: in "Net/TestFaceUri/CanonizeUdpV4": udp4://192.0.2.7:99999 should fail
../tests/unit-tests/net/face-uri.t.cpp(88): error: in "Net/TestFaceUri/CanonizeUdpV6": udp6://[2001:db8::1]:99999 should fail
../tests/unit-tests/net/face-uri.t.cpp(101): error: in "Net/TestFaceUri/CanonizeUdpV6": udp6://google-public-dns-a.google.com should succeed
../tests/unit-tests/net/face-uri.t.cpp(97): error: in "Net/TestFaceUri/CanonizeUdpV6": check tc->m_isCompleted == false has failed [true != false]
../tests/unit-tests/net/face-uri.t.cpp(59): error: in "Net/TestFaceUri/CanonizeUdpV6": check m_nPending == 0 has failed [-1 != 0]
../tests/unit-tests/net/face-uri.t.cpp(88): error: in "Net/TestFaceUri/CanonizeTcpV4": tcp4://192.0.2.7:99999 should fail
../tests/unit-tests/net/face-uri.t.cpp(88): error: in "Net/TestFaceUri/CanonizeTcpV6": tcp6://[2001:db8::1]:99999 should fail
../tests/unit-tests/net/face-uri.t.cpp(101): error: in "Net/TestFaceUri/CanonizeTcpV6": tcp6://google-public-dns-a.google.com should succeed
../tests/unit-tests/net/face-uri.t.cpp(97): error: in "Net/TestFaceUri/CanonizeTcpV6": check tc->m_isCompleted == false has failed [true != false]
../tests/unit-tests/net/face-uri.t.cpp(59): error: in "Net/TestFaceUri/CanonizeTcpV6": check m_nPending == 0 has failed [-1 != 0]
../tests/unit-tests/net/face-uri.t.cpp(428): error: in "Net/TestFaceUri/ParseUnix": check uri.parse("unix://var/run/example.sock") == false has failed [true != false]
../tests/unit-tests/net/face-uri.t.cpp(498): error: in "Net/TestFaceUri/ParseDev": check uri.parse("dev://eth0:8888") == false has failed [true != false]

*** 13 failures are detected (7 failures are expected) in the test module "ndn-cxx Tests"

yeah it's DNS-related.

We can/should add a /etc/hosts entry for google-public-dns-a.google.com to all jenkins slaves.

Davide Pesavento wrote:

We can/should add a /etc/hosts entry for google-public-dns-a.google.com to all jenkins slaves.

This doesn't fix the issue on my local VM, even if I add the IPv4 and v6 addresses to /etc/hosts. Additionally, I noticed that it only fails for IPv6, which my ISP supports (and gives me an IP address for). However, while I am able to use v6 from my computer, I am unable to do so from within Virtualbox.

Eric Newberry wrote:

This doesn't fix the issue on my local VM, even if I add the IPv4 and v6 addresses to /etc/hosts.

That's odd. What's the content of /etc/nsswitch.conf on the vm?

Davide Pesavento wrote:

Eric Newberry wrote:

This doesn't fix the issue on my local VM, even if I add the IPv4 and v6 addresses to /etc/hosts.

That's odd. What's the content of /etc/nsswitch.conf on the vm?

/etc/nsswitch.conf:

# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.

passwd:         compat
group:          compat
shadow:         compat
gshadow:        files

hosts:          files mdns4_minimal [NOTFOUND=return] dns myhostname
networks:       files

protocols:      db files
services:       db files
ethers:         db files
rpc:            db files

netgroup:       nis

I went ahead and created my own Vagrant base box for artful. I'm going to deploy some agents running on it and see if they work.

I didn't run into any of the above DNS issues with ndn-cxx in the Vagrant agent I set up. I'm deploying a second agent and will add them to Jenkins shortly. After this is complete, I will retire the 17.04 agents.