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.
This commit is contained in:
Daniel Chiquito committed 2024-03-09 18:22:57 -05:00
1 parent ead42beff6
commit de7e4e49da
1 file changed
+4
+4
View File
@@ -2161,12 +2161,16 @@ class ISOTPTest(unittest.TestCase):
with socket.socket(socket.PF_CAN, socket.SOCK_DGRAM, socket.CAN_ISOTP) as s:
pass
# TODO: RUSTPYTHON, OSError: bind(): bad family
@unittest.expectedFailure
def testTooLongInterfaceName(self):
# most systems limit IFNAMSIZ to 16, take 1024 to be sure
with socket.socket(socket.PF_CAN, socket.SOCK_DGRAM, socket.CAN_ISOTP) as s:
with self.assertRaisesRegex(OSError, 'interface name too long'):
s.bind(('x' * 1024, 1, 2))
# TODO: RUSTPYTHON, OSError: bind(): bad family
@unittest.expectedFailure
def testBind(self):
try:
with socket.socket(socket.PF_CAN, socket.SOCK_DGRAM, socket.CAN_ISOTP) as s: