Bug #3270
closed
Occasional non-reproducible test failure in UtilDns/AsynchronousV6
Added by susmit shannigrahi about 9 years ago.
Updated almost 7 years ago.
Description
I have seen this a couple of times but it's not easy to reproduce.
+ build/unit-tests
Running 607 test cases...
../tests/unit-tests/util/dns.t.cpp(79): fatal error: in "UtilDns/AsynchronousV6": Resolution should not have failed
*** 1 failure is detected in the test module "ndn-cxx Unit Tests"
Files
- Tracker changed from Task to Bug
- Subject changed from Occasional non-reproducable test failure in "UtilDns/AsynchronousV6" to Occasional non-reproducible test failure in UtilDns/AsynchronousV6
- Description updated (diff)
- Start date deleted (
10/16/2015)
I used to see these failures months ago too. Then they stopped, so I assumed either a system resolver bug fixed by an update, or a faulty/misconfigured DNS server. The root cause could also be the same as #2148.
Any chance you can capture a full packet trace of a failing execution? You can run only this particular test with -t UtilDns/AsynchronousV6.
- Related to Bug #2148: UtilFaceUri/Canonize{Tcp,Udp} test cases randomly time out on Ubuntu 14.10 added
Maybe related: When I try to execute nfdc register / tcp4://hobo.cs.arizona.edu on a VM in a laptop, I'm getting ERROR: Canonize faceUri failed : Timeout.
tcpdump trace reveals DNS queries are sent for both A and AAAA records, but the DNS server responds to A record query only.
I tried different machines but I haven't been able to reproduce it yet.
Junxiao Shi wrote:
tcpdump trace reveals DNS queries are sent for both A and AAAA records, but the DNS server responds to A record query only.
But you do get one valid A reply... so why is it considered a timeout failure?
Furthermore, since we're resolving for tcp4://, we should send out queries for A records only.
Package has been approved but we still need to address this.
- Target version changed from v0.4 to v0.5
- Target version deleted (
v0.5)
- Has duplicate Bug #2786: UtilDns test suite fails with some (faulty?) DNS resolver configuration added
- Status changed from New to Feedback
- Status changed from Feedback to Closed
Let's close this for now. Please reopen if it happens again.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by