View Revisions: Issue #5046
[ All Revisions ] [ Back to Issue ]
| Summary | 0005046: testUDPListener: something is wrong with the 32bit mingw buildbot | ||
|---|---|---|---|
| Revision | 2016-01-26 06:09 by jK | ||
| Description | see: http://buildbot.springrts.com/builders/full-windows-test/builds/3708/steps/test/logs/stdio -> 1: Running 1 test case... 1: Binding UDP socket to IP (v4) 127.0.0.1 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 11111 1: Binding UDP socket to IP (v6) :: port 11111 1: Warning: Opening socket on loopback address. Other users will not be able to connect! 1: Binding UDP socket to IP (v6) ::1 port 11111 1: Binding UDP socket to IP (v6) ::2 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) fe80::224:1dff:fecf:df44 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) fe80:: port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) ::1 port 11111 1: Warning: Opening socket on loopback address. Other users will not be able to connect! 1: Binding UDP socket to IP (v4) 173.194.112.105 port 11111 1: err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0060. 1: Binding UDP socket to IP (v6) :: port 1024 1: Binding UDP socket to IP (v6) :: port 11111 1: Binding UDP socket to IP (v6) :: port 32000 1: Binding UDP socket to IP (v6) :: port 65535 see the multiple "Binding UDP socket to IP (v4) 0.0.0.0 port 0" after of the intentional wrong IPv6 addresses? Neither the test code nor the engine code include that. Nor does any other buildbot include that lines. So what makes the 32bit mingw buildbot trying to connect to "0.0.0.0:0" after wrong IPv6 addresses? |
||
| Revision | 2016-01-26 02:45 by jK | ||
| Description | see: http://buildbot.springrts.com/builders/full-windows-test/builds/3708/steps/test/logs/stdio -> 1: Running 1 test case... 1: Binding UDP socket to IP (v4) 127.0.0.1 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 11111 1: Binding UDP socket to IP (v6) :: port 11111 1: Warning: Opening socket on loopback address. Other users will not be able to connect! 1: Binding UDP socket to IP (v6) ::1 port 11111 1: Binding UDP socket to IP (v6) ::2 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) fe80::224:1dff:fecf:df44 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) fe80:: port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) ::1 port 11111 1: Warning: Opening socket on loopback address. Other users will not be able to connect! 1: Binding UDP socket to IP (v4) 173.194.112.105 port 11111 1: err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0060. 1: Binding UDP socket to IP (v6) :: port 1024 1: Binding UDP socket to IP (v6) :: port 11111 1: Binding UDP socket to IP (v6) :: port 32000 1: Binding UDP socket to IP (v6) :: port 65535 see the multiple "Binding UDP socket to IP (v4) 0.0.0.0 port 0" in front of the intentional wrong IPv6 addresses? Neither the test code nor the engine code include that. Nor does any other buildbot include that lines. So what makes the 32bit mingw buildbot trying to connect to "0.0.0.0:0" before wrong IPv6 addresses? |
||
| Revision | 2016-01-26 02:43 by jK | ||
| Description | see: http://buildbot.springrts.com/builders/full-windows-test/builds/3708/steps/test/logs/stdio -> 1: Running 1 test case... 1: Binding UDP socket to IP (v4) 127.0.0.1 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 11111 1: Binding UDP socket to IP (v6) :: port 11111 1: Warning: Opening socket on loopback address. Other users will not be able to connect! 1: Binding UDP socket to IP (v6) ::1 port 11111 1: Binding UDP socket to IP (v6) ::2 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) fe80::224:1dff:fecf:df44 port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) fe80:: port 11111 1: Binding UDP socket to IP (v4) 0.0.0.0 port 0 1: ../../test/engine/System/Net/TestUDPListener.cpp(20): error in "TryBindSocket": 1: Binding UDP socket to IP (v6) ::1 port 11111 1: Warning: Opening socket on loopback address. Other users will not be able to connect! 1: Binding UDP socket to IP (v4) 173.194.112.105 port 11111 1: err:winsock:interface_bind Failed to bind to interface, receiving broadcast packets will not work on socket 0060. 1: Binding UDP socket to IP (v6) :: port 1024 1: Binding UDP socket to IP (v6) :: port 11111 1: Binding UDP socket to IP (v6) :: port 32000 1: Binding UDP socket to IP (v6) :: port 65535 see the multiple "Binding UDP socket to IP (v4) 0.0.0.0 port 0" in front of the intentional wrong IPv6 addresses? Neither the test code nor the engine code include that. Nor are any other buildbot include that lines. So what makes the 32bit mingw buildbot trying to connect to "0.0.0.0:0" before wrong IPv6 addresses? |
||