Skip site navigation (1)Skip section navigation (2) 
Date:      Thu, 08 Jun 2017 22:18:47 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-testing@freebsd.org
Subject:   [Bug 219874] lib/libc/tests/nss/gethostby_test is failing sporadically
Message-ID:  <bug-219874-32464@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219874

            Bug ID: 219874
           Summary: lib/libc/tests/nss/gethostby_test is failing
                    sporadically
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: tests
          Assignee: freebsd-testing@freebsd.org
          Reporter: ngie@FreeBSD.org

I'm running into periodic issues with some of the subtestcases, in particul=
ar,
:getipnodebyname_getaddrinfo_ipv6, e.g.,

using getaddrinfo() to resolve localhost
using getaddrinfo() to resolve anoncvs.cirr.com
using getaddrinfo() to resolve anoncvs.netbsd.se
using getaddrinfo() to resolve antioche.antioche.eu.org
using getaddrinfo() to resolve centaurus.4web.cz
using getaddrinfo() to resolve ntp.math.ntnu.no
using getaddrinfo() to resolve console.netbsd.org
using getaddrinfo() to resolve cvs.netbsd.org
using getaddrinfo() to resolve cvsup.netbsd.se
using getaddrinfo() to resolve ftp.chg.ru
using getaddrinfo() to resolve ftp.estpak.ee
using getaddrinfo() to resolve ftp.fsn.hu
using getaddrinfo() to resolve ftp.funet.fi
using getaddrinfo() to resolve ftp.netbsd.org
using getaddrinfo() to resolve ftp.nluug.nl
using getaddrinfo() to resolve ftp.plig.net
using getaddrinfo() to resolve ftp.rrze.uni-erlangen.de
using getaddrinfo() to resolve ftp.xgate.co.kr
using getaddrinfo() to resolve gd.tuwien.ac.at
using getaddrinfo() to resolve gort.ludd.luth.se
using getaddrinfo() to resolve chat.freenode.net
not equal - one of he->h_addr_list couldn't be found
not ok - addrinfo and hostent are not equal

I'm trying to add more logging to determine why the issue is occurring, sin=
ce
the current information is insufficient.

This has been seen on a Comcast consumer networked machine and multiple Dell
EMC networked machines.

The issue might be flaky DNS resolved names/address, intermittent connection
issues, or an issue with the resolver software. Not enough information is k=
nown
at this time to point a specific finger at the root cause.

--=20
You are receiving this mail because:
You are the assignee for the bug.=

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219874-32464>