Commit 83cbf31
test: avoid usage of mixed IPV6 addresses
The test case fails in AIX due to the mixed-use of unspecified
and loopback addresses. This is not a problem in most platforms
but fails in AIX. (In Windows too, but does not manifest as the
test is omitted in Windows for a different reason).
There exists no documented evidence which supports the mixed use
of unspecified and loopback addresses.
While AIX strictly follows the IPV6 specification with respect to
unspecified address ('::') and loopback address ('::1'), the test
case latches on to the behavior exhibited by other platforms,
and hence it fails in AIX.
The proposed fix is to make it work in all platforms including
AIX by using the loopback address for the client to connect,
as that is the address at which the server listens.
Fixes: #7563
PR-URL: #7702
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>1 parent 4b320ad commit 83cbf31
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -92,7 +92,7 @@ if (cluster.isMaster) { | |||
| 92 | 92 | debugger; | |
| 93 | 93 | }; | |
| 94 | 94 | if (common.hasIPv6) | |
| 95 | - server.listen(cb); | ||
| 95 | + server.listen(0, '::1', cb); | ||
| 96 | 96 | else | |
| 97 | 97 | server.listen(0, common.localhostIPv4, cb); | |
| 98 | 98 | process.on('disconnect', process.exit); | |
0 commit comments