test-http-dns-fail.js failing on Jenkins

[misterdjules]

test-http-dns-fail.js was in the list of flaky tests at some point, and then got removed from the list of flaky tests when all Jenkins agent stopped using the specific DNS server(s) that do not respond with an error when trying to resolve a clearly invalid hostname.

Now that we started using the CI platform at jenkins-iojs.nodesource.com, some of the Jenkins agents that this platform uses still trigger a failure for this test. It could be because these agents are still configured to use these "faulty" DNS servers.

@orangemocha @joaocgreis @jbergstroem @rvagg Would you mind checking if these SmartOS CI agents still have 4.2.2.2 in /etc/resolv.conf? I currently can't access a shell on these agents.

[joaocgreis]

I added 4.2.2.2 in the 32 bit Smart OS machine (was already there in the 64 bit one).

[joaocgreis]

... but that was not the machine where the test failed. Let me try to run it manually there.

[joaocgreis]

@misterdjules @orangemocha Ok, the objective was to remove it, not add it. Sorry for the confusion, it is fixed now and works.

@jbergstroem @rvagg on the 64 bit machine, there was also a 216.52.1.1 server in /etc/resolv.conf, because of it the test took 1 full minute to complete. I commented that line. Is it ok to remove completely or was there for some reason?

[misterdjules]

@joaocgreis Thank you 👍 Can we close this issue then?

[jbergstroem]

@joaocgreis not sure where that came from. Happy to let it go.

[joaocgreis]

@jbergstroem ok, preparing PR.

@misterdjules sure, seems all ok now.