3f1df4bacb
Only a few ports have TCP/IP loopback enabled in their network stack, and this test will only pass on those ports. There's not really any good way to do a feature check for loopback mode without actually running the test and seeing if it passes/fails, so add an explicit check that the test is running on a port known to support loopback. (Enabling loopback on lwIP, eg RPI_PICO_W, costs +568 code and +272 bss and is a rarely used feature, so not worth unconditionally enabling.) 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.py | ||
| connect_nonblock.py.exp | ||
| connect_nonblock_xfer.py | ||
| 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