You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
investigate flaky internet/test-dns-idna2008 test #25870
I guess ESERVFAIL is a DNS problem likely unrelated to the test itself? Although other DNS tests in internet ran just fine, so maybe it is in fact specific to this test?
It's been a one-time failure so far? ESERVFAIL is reported by the DNS server; could be a temporary service outage.
I had the temporary-hiccup idea too, but other DNS tests in the internet suite didn't fail. Still, the implication I'm getting from your comment--that there's probably not much point in chasing it down unless we see it more than once--is no doubt correct. Maybe leave this open for a bit and close it after a week or so if we don't see it again?
I'll take a look but I wonder if it's an environmental issue (i.e., network issue) because it never fails for me locally. What about you?
I've not had it fail locally either. It passed in last night's run on test-rackspace-ubuntu1604-x64-2.
To get a baseline (or to see if it passes 7 times, and then the firewall kicks in and it fails the remaining 93 times or whatever), here's 100 runs in CI:
To get a baseline (or to see if it passes 7 times, and then the firewall kicks in and it fails the remaining 93 times or whatever), here's 100 runs in CI:
It failed again today. So it failed each of the last three runs. (The test is run once a day in CI.) Interesting that when it fails, it fails reliably. And when it doesn't fail, it doesn't fail at all.
Ooh, this time around things are different from when initially reported. The test is taking 30 seconds or so before failing. Probably some throttling going on somewhere, yeah? I'm logged on and will try running the lookups/resolves in series rather than in parallel and see if that does anything...
@Trott I've (temporarily) unpinned this issue as we can only have three pinned and I think the current test breakage on master (#26528) should definitely be pinned. We can swap then back when master is unbroken.
So... node-daily-master is unbroke.
But... this test will still be flaky if the system's DNS server fail to resolve straße.de.
.
.
.
I just had an idea: pass the dns.lookup test if the error is Error: queryA ESERVFAIL straße.de since IIUC it mean node passed the correct query to the OS.
Activity
bnoordhuis commentedon Feb 1, 2019
It's been a one-time failure so far?
ESERVFAILis reported by the DNS server; could be a temporary service outage.Trott commentedon Feb 2, 2019
I had the temporary-hiccup idea too, but other DNS tests in the
internetsuite didn't fail. Still, the implication I'm getting from your comment--that there's probably not much point in chasing it down unless we see it more than once--is no doubt correct. Maybe leave this open for a bit and close it after a week or so if we don't see it again?Trott commentedon Feb 2, 2019
Failed again today:
https://ci.nodejs.org/job/node-test-commit-custom-suites/856/default/console
test-rackspace-ubuntu1604-x64-1
bnoordhuis commentedon Feb 3, 2019
I'll take a look but I wonder if it's an environmental issue (i.e., network issue) because it never fails for me locally. What about you?
Trott commentedon Feb 3, 2019
I've not had it fail locally either. It passed in last night's run on test-rackspace-ubuntu1604-x64-2.
To get a baseline (or to see if it passes 7 times, and then the firewall kicks in and it fails the remaining 93 times or whatever), here's 100 runs in CI:
https://ci.nodejs.org/job/node-stress-single-test/2147/
Trott commentedon Feb 3, 2019
No failures in stress test on test-rackspace-ubuntu1604-x64-2.
Re-running, but with all
internettests, but only 10 consecutive runs:https://ci.nodejs.org/job/node-stress-single-test/2148/
Trott commentedon Feb 3, 2019
Also successful on test-rackspace-ubuntu1604-x64-2.
¯\(ツ)/¯
Trott commentedon Mar 3, 2019
Happened in CI again today.
https://ci.nodejs.org/job/node-test-commit-custom-suites/897/default/console
test-rackspace-ubuntu1604-x64-1
Trott commentedon Mar 4, 2019
Again today:
https://ci.nodejs.org/job/node-test-commit-custom-suites/898/default/console
test-rackspace-ubuntu1604-x64-1
Trott commentedon Mar 5, 2019
It failed again today. So it failed each of the last three runs. (The test is run once a day in CI.) Interesting that when it fails, it fails reliably. And when it doesn't fail, it doesn't fail at all.
https://ci.nodejs.org/job/node-test-commit-custom-suites/899/default/console
test-rackspace-ubuntu1604-x64-1
Trott commentedon Mar 5, 2019
@nodejs/build Thoughts on this one?
Trott commentedon Mar 5, 2019
Ooh, this time around things are different from when initially reported. The test is taking 30 seconds or so before failing. Probably some throttling going on somewhere, yeah? I'm logged on and will try running the lookups/resolves in series rather than in parallel and see if that does anything...
6 remaining items
richardlau commentedon Mar 8, 2019
@Trott I've (temporarily) unpinned this issue as we can only have three pinned and I think the current test breakage on master (#26528) should definitely be pinned. We can swap then back when master is unbroken.
refack commentedon Mar 8, 2019
So...
node-daily-masteris unbroke.But... this test will still be flaky if the system's DNS server fail to resolve
straße.de..
.
.
I just had an idea: pass the
dns.lookuptest if the error isError: queryA ESERVFAIL straße.desince IIUC it mean node passed the correct query to the OS.test: de-flake test-dns-idna2008.js
refack commentedon Mar 10, 2019
https://ci.nodejs.org/job/node-test-commit-custom-suites-freestyle/5173/testReport/junit/(root)/test/internet_test_dns_idna2008/, but but but, it passed CI!?
fix of fix in #26570
test: fix syntax error in test-dns-idna2008.js when failing
test: de-flake test-dns-idna2008.js
test: fix syntax error in test-dns-idna2008.js when failing
test: de-flake test-dns-idna2008.js
test: fix syntax error in test-dns-idna2008.js when failing
test: fix syntax error in test-dns-idna2008.js when failing
test: fix syntax error in test-dns-idna2008.js when failing
test: fix test-dns-idna2008.js
test: fix test-dns-idna2008.js