Skip to content

Commit de7e4e4

Browse files
committed
Disable broken test_socket.py tests
There are a substantial number of socket tests that are disabled due to `bind(): bad family` errors. It seems like RustPython only supports a small subset of the required connection families, so the failing tests are broken for the same reasons.
1 parent ead42be commit de7e4e4

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

‎Lib/test/test_socket.py‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2161,12 +2161,16 @@ def testCreateISOTPSocket(self):
21612161
with socket.socket(socket.PF_CAN, socket.SOCK_DGRAM, socket.CAN_ISOTP) as s:
21622162
pass
21632163

2164+
# TODO: RUSTPYTHON, OSError: bind(): bad family
2165+
@unittest.expectedFailure
21642166
def testTooLongInterfaceName(self):
21652167
# most systems limit IFNAMSIZ to 16, take 1024 to be sure
21662168
with socket.socket(socket.PF_CAN, socket.SOCK_DGRAM, socket.CAN_ISOTP) as s:
21672169
with self.assertRaisesRegex(OSError, 'interface name too long'):
21682170
s.bind(('x' * 1024, 1, 2))
21692171

2172+
# TODO: RUSTPYTHON, OSError: bind(): bad family
2173+
@unittest.expectedFailure
21702174
def testBind(self):
21712175
try:
21722176
with socket.socket(socket.PF_CAN, socket.SOCK_DGRAM, socket.CAN_ISOTP) as s:

0 commit comments

Comments
 (0)