Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

Failed test: test-net-connect-options-ipv6 #7983

Closed
jbergstroem opened this issue Jul 22, 2014 · 8 comments
Closed

Failed test: test-net-connect-options-ipv6 #7983

jbergstroem opened this issue Jul 22, 2014 · 8 comments

Comments

@jbergstroem
Copy link
Member

I get two failed tests on 0.11.13 because one of my test rigs "lacks" ipv6 support:

=== release test-net-connect-options-ipv6 ===                                  
Path: simple/test-net-connect-options-ipv6
exit false false
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: listen EAFNOSUPPORT
    at exports._errnoException (util.js:742:11)
    at Server._listen2 (net.js:1128:19)
    at listen (net.js:1170:10)
    at net.js:1253:9
    at dns.js:82:18
    at process._tickCallback (node.js:343:11)
Command: out/Release/node /var/tmp/portage/net-libs/nodejs-0.11.13/work/node-v0.11.13/test/simple/test-net-connect-options-ipv6.js
=== release test-net-pingpong ===                                   
Path: simple/test-net-pingpong
/var/tmp/portage/net-libs/nodejs-0.11.13/work/node-v0.11.13/test/tmp/test.sock
server listening on /var/tmp/portage/net-libs/nodejs-0.11.13/work/node-v0.11.13/test/tmp/test.sock undefined
server listening on 12346 undefined
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: listen EAFNOSUPPORT
    at exports._errnoException (util.js:742:11)
    at Server._listen2 (net.js:1128:19)
    at listen (net.js:1170:10)
    at net.js:1253:9
    at dns.js:82:18
    at process._tickCallback (node.js:343:11)
    at Function.Module.runMain (module.js:492:11)
    at startup (node.js:124:16)
    at node.js:807:3

Perhaps ipv6 support should be checked and then skip tests requiring it?

This is a 64-bit linux 3.15 on glib 2.19 if relevant.

@indutny
Copy link
Member

indutny commented Jul 31, 2014

I think it is fixed now?

@indutny indutny closed this as completed Jul 31, 2014
@jbergstroem
Copy link
Member Author

Unfortunately not. Tested with d287b8e:

=== release test-net-connect-options-ipv6 ===                                  
Path: simple/test-net-connect-options-ipv6
exit false false
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: listen EAFNOSUPPORT
    at exports._errnoException (util.js:742:11)
    at Server._listen2 (net.js:1110:19)
    at listen (net.js:1154:10)
    at net.js:1237:9
    at dns.js:82:18
    at process._tickCallback (node.js:343:11)
Command: out/Release/node /home/jbergstroem/node/test/simple/test-net-connect-options-ipv6.js
=== release test-net-pingpong ===                                   
Path: simple/test-net-pingpong
/home/jbergstroem/node/test/tmp/test.sock
server listening on /home/jbergstroem/node/test/tmp/test.sock undefined
server listening on 12346 undefined
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: listen EAFNOSUPPORT
    at exports._errnoException (util.js:742:11)
    at Server._listen2 (net.js:1110:19)
    at listen (net.js:1154:10)
    at net.js:1237:9
    at dns.js:82:18
    at process._tickCallback (node.js:343:11)
    at Function.Module.runMain (module.js:503:11)
    at startup (node.js:124:16)
    at node.js:811:3
Command: out/Release/node /home/jbergstroem/node/test/simple/test-net-pingpong.js

@jbergstroem
Copy link
Member Author

simple/test-dgram-bind-default-address has the same issue.

@jbergstroem
Copy link
Member Author

@indutny reopen? Should I provide strace output?

@indutny indutny reopened this Aug 2, 2014
indutny added a commit to indutny/node that referenced this issue Aug 2, 2014
@jbergstroem
Copy link
Member Author

@indutny simple/test-net-connect-options-ipv6.js also needs it, otherwise all good. I haven't tried the tests living in test/internetyet, just what make check would provide.

@indutny
Copy link
Member

indutny commented Aug 2, 2014

Should be fixed by #8060

@jbergstroem
Copy link
Member Author

Sorry, typoed on my previous comment. I was referring to simple/test-net-pingpong.js. I'll leave a comment in there too.

indutny added a commit to indutny/node that referenced this issue Aug 2, 2014
misterdjules pushed a commit to misterdjules/node that referenced this issue Aug 12, 2014
indutny added a commit that referenced this issue Aug 12, 2014
fix #7983
fix #8049

Conflicts:
	test/common.js
indutny added a commit that referenced this issue Aug 13, 2014
fix #7983
fix #8049

Conflicts:
	test/common.js
fiveisprime pushed a commit to fiveisprime/node that referenced this issue Aug 17, 2014
fix nodejs#7983
fix nodejs#8049

Signed-off-by: Timothy J Fontaine <tjfontaine@gmail.com>
@k1ng440
Copy link

k1ng440 commented Nov 9, 2014

i am still having this issue on windows 8.1.

npm WARN package.json Nikebot-6-logger@0.0.1 No repository field.
npm WARN package.json Nikebot-6-logger@0.0.1 No README data
npm ERR! Error: connect EAFNOSUPPORT
npm ERR! at errnoException (net.js:904:11)
npm ERR! at connect (net.js:766:19)
npm ERR! at net.js:845:9
npm ERR! at asyncCallback (dns.js:68:16)
npm ERR! at Object.onanswer as oncomplete
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/npm/npm/issues

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install" "socket.io"
npm ERR! cwd D:\logger
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! syscall connect
npm ERR! code EAFNOSUPPORT
npm ERR! errno EAFNOSUPPORT
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! D:\logger\npm-debug.log
npm ERR! not ok code 0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants