-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v18.x - test-dns-ipv6 fails in 18.17.0 and later #49203
Comments
I did some bisection as part of #49183 which was what led me to open this issue. |
Using git bisect it seems to indicate that it was this PR that causes the failure:
|
@anonrig can you take a look at the backport and see if you can spot why it might be causing that test to fail? |
We had a similar issue in the past: #48262. Might be related to it. I'll take a look at it soon. I think we should backport these 2 pull requests as well: |
I think this is caused by calling https://github.com/nodejs/node/blob/v18.x-staging/lib/internal/idna.js#L3 |
Refs: nodejs#49203 Changes slipped into v18.x regressed test/internet/test-dns-ipv6 as I assume the action did not run because no test under test/internet was changed. Add some of the common paths that include code that might introduce failures in the internet tests. Signed-off-by: Michael Dawson <[email protected]>
Does this issue persist with the v18 proposal? |
Refs: #49203 Changes slipped into v18.x regressed test/internet/test-dns-ipv6 as I assume the action did not run because no test under test/internet was changed. Add some of the common paths that include code that might introduce failures in the internet tests. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #49218 Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: #49203 Changes slipped into v18.x regressed test/internet/test-dns-ipv6 as I assume the action did not run because no test under test/internet was changed. Add some of the common paths that include code that might introduce failures in the internet tests. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #49218 Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
This was fixed in Node.js 18.18.0. |
Refs: #49203 Changes slipped into v18.x regressed test/internet/test-dns-ipv6 as I assume the action did not run because no test under test/internet was changed. Add some of the common paths that include code that might introduce failures in the internet tests. Signed-off-by: Michael Dawson <[email protected]> PR-URL: #49218 Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/node#49203 Changes slipped into v18.x regressed test/internet/test-dns-ipv6 as I assume the action did not run because no test under test/internet was changed. Add some of the common paths that include code that might introduce failures in the internet tests. Signed-off-by: Michael Dawson <[email protected]> PR-URL: nodejs/node#49218 Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Refs: nodejs/node#49203 Changes slipped into v18.x regressed test/internet/test-dns-ipv6 as I assume the action did not run because no test under test/internet was changed. Add some of the common paths that include code that might introduce failures in the internet tests. Signed-off-by: Michael Dawson <[email protected]> PR-URL: nodejs/node#49218 Reviewed-By: Ruy Adorno <[email protected]> Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Moshe Atlow <[email protected]> Reviewed-By: Luigi Pinca <[email protected]>
Version
v18.17.0
Platform
at least linux
Subsystem
net
What steps will reproduce the bug?
tools/test.py test/internet/test-dns-ipv6
How often does it reproduce? Is there a required condition?
100%
What is the expected behavior? Why is that the expected behavior?
Test passes
What do you see instead?
Test passes
Additional information
No response
The text was updated successfully, but these errors were encountered: