parallel/test-https-connect-address-family and parallel/test-tls-connect-address-family failures

[mhdawson]

• Version: Master
• Platform: several linuxes
• Subsystem: net

parallel/test-https-connect-address-family/parallel/test-tls-connect-address-family

have started failing this morning on ppc le runs, was only running plinux job so not sure yet about other platforms.

https://ci.nodejs.org/job/node-test-commit-plinux/2974/nodes=ppcle-ubuntu1404/console

not ok 570 parallel/test-https-connect-address-family
# events.js:160
#       throw er; // Unhandled 'error' event
#       ^
# 
# Error: getaddrinfo ENOTFOUND localhost localhost:12446
#     at errnoException (dns.js:28:10)
#     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:79:26)
  ---
  duration_ms: 2.413

not ok 951 parallel/test-tls-connect-address-family
# events.js:160
#       throw er; // Unhandled 'error' event
#       ^
# 
# Error: getaddrinfo ENOTFOUND localhost localhost:12646
#     at errnoException (dns.js:28:10)
#     at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:79:26)
  ---
  duration_ms: 0.272

[mhdawson]

Broader linux run to see if is just linux ppcle or not

https://ci.nodejs.org/job/node-test-commit-linux/3906/

[mhdawson]

Possibly related to https://github.com/nodejs/node/search?q=https-connect-address-family&type=Issues&utf8=%E2%9C%93, but not sure why we are seeing failures now.

[mhdawson]

Seems to be failing on other linux variants as well

[mhdawson]

Looks like this is still in the parallel.status so not sure what is going on:

# Flaky until https://github.com/nodejs/build/issues/415 is resolved.
# On some of the buildbots, AAAA queries for localhost don't resolve
# to an address and neither do any of the alternatives from the
# localIPv6Hosts list from test/common.js.
test-https-connect-address-family : PASS,FLAKY
test-tls-connect-address-family : PASS,FLAKY

[Trott]

@nodejs/testing

[gibfahn]

I believe this is the same issue as #7288

[mhdawson]

@gibm that was the link I tried to include in the earlier comment but did not get the link right. What's strange is that the test was actually failing in the community CI even though it was marked as flaky. It seems to be passing again in the community CI runs so I'm closing this one.