df0d7e9429
If the socket timeout is 0 then a failed socket.connect() raises EINPROGRESS (which is what the lwIP bindings already did), but if the socket timeout is non-zero then a failed socket.connect() should raise ETIMEDOUT. The latter is fixed in this commit. A test is added for these timeout cases. Signed-off-by: Damien George <damien@micropython.org> |
||
---|---|---|
.. | ||
accept_nonblock.py | ||
accept_nonblock.py.exp | ||
accept_timeout.py | ||
accept_timeout.py.exp | ||
asyncio_loopback.py | ||
asyncio_loopback.py.exp | ||
asyncio_start_server.py | ||
asyncio_start_server.py.exp | ||
connect_nonblock_xfer.py | ||
connect_nonblock.py | ||
connect_nonblock.py.exp | ||
connect_poll.py | ||
connect_poll.py.exp | ||
connect_timeout.py | ||
README | ||
ssl_getpeercert.py | ||
ssl_getpeercert.py.exp | ||
ssl_verify_callback.py | ||
ssl_verify_callback.py.exp |
This directory contains network tests which require just "peer to peer" network connection between test host and device under test, instead of full Internet connection. Note that setup for these tests and tests themselves are WIP, and may not yet fully correspond to the functional specification above. So far, these tests are not run as part of the main testsuite and need to be run separately (from the main test/ directory): ./run-tests.py net_hosted/*.py