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
test-dgram-udp6-link-local-address failing on AIX 7.1 Node.js 12 #39143
Comments
Line 363 of Lines 360 to 363 in 4cdb240
|
Added some printf statements to get the value of |
So far I've been able to determine that we get an IPv6 link local address with scope id 0 and that causes For the last working build the test was actually skipped:
Somehow between 18 June and 19 June we gained an IPv6 link local address. |
libuv test fails on the same machines:
|
I'm not entirely sure the assumption in de174cd about link local addresses always being scoped is correct -- on AIX the link local address I can see on the interface does not appear to be scoped and https://www.ibm.com/docs/en/aix/7.2?topic=6-ipv6-multihomed-link-local-site-local-support seems to indicate options to control how AIX handles link local addresses without any mention of scoping. In any case I had a discussion with @AshCripps who remembered that he had to remove the
the
I'm going to remove the interface so that we're back to the state we were in before and we can get a clean CI run for Node.js 12 for the upcoming security release next week but I'll keep this issue open as I think there's a mismatch somewhere between assumptions in libuv/Node.js and AIX with regards to IPv6 link local addresses and scope ids. |
FWIW Node.js 14 compiled on the AIX 7.1 machine (we can't run the binaries compiled for AIX 7.2 on AIX 7.1 so need to compile from source) exhibits the same test failure. We don't see failures with Node.js 14, 16 and master as they run on the AIX 7.2 machines at OSUOSL and those do not have any IPv6 addresses configured on their network interfaces. |
With the interface disabled CI now passes: https://ci.nodejs.org/job/node-test-commit-aix/37278/nodes=aix71-ppc64/ |
I've also removed the |
@richardlau this looks like the same crash as the one reported in #41500 which got fixed in #41547. Do we need to wait for the commits to land on v12.x before we can close this issue? |
@RaisinTen I haven't had the time to reenable the en1 and sit0 interfaces (i.e. the ones with IPv6 addresses) that were triggering the issue to verify the problem has been resolved. |
Closing this issue because v12.x goes EOL at the end of this month and no more releases are planned. |
This test started failing 5 days ago (19 June 2021) in https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix71-ppc64/37210/ and has been consistently failing in every build since.
We only build/test on AIX 7.1 for Node.js 12 now, so every run is Node.js 12. Furthermore the last passing build, https://ci.nodejs.org/job/node-test-commit-aix/nodes=aix71-ppc64/37194/, built the same commit 4cdb240 as the first failing build, so this wasn't due to a code change (although it's possibly an exposure of a latent bug we hadn't seen before).
I forced recent builds onto test-ibm-aix71-ppc64_be-4 (as Jenkins had stickied runs onto test-ibm-aix71-ppc64_be-3 and the test fails there too so it's not machine specific.
cc @nodejs/platform-aix
The text was updated successfully, but these errors were encountered: