summaryrefslogtreecommitdiffstatshomepage
path: root/tests/net_hosted/asyncio_loopback.py
diff options
context:
space:
mode:
authorDamien George <damien@micropython.org>2025-04-29 10:24:52 +1000
committerAngus Gratton <gus@projectgus.com>2025-05-01 11:16:29 +1000
commit3f1df4bacb2aa8f9018011c6a61eff9247248e1b (patch)
tree5a6d29467b9c4e622e3c4b82874b501431e67913 /tests/net_hosted/asyncio_loopback.py
parent62479f2cb60ae73dcb81d0b0e2b2d147813e0604 (diff)
downloadmicropython-3f1df4bacb2aa8f9018011c6a61eff9247248e1b.tar.gz
micropython-3f1df4bacb2aa8f9018011c6a61eff9247248e1b.zip
tests/net_hosted: Only run network loopback test on supported targets.
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>
Diffstat (limited to 'tests/net_hosted/asyncio_loopback.py')
-rw-r--r--tests/net_hosted/asyncio_loopback.py7
1 files changed, 7 insertions, 0 deletions
diff --git a/tests/net_hosted/asyncio_loopback.py b/tests/net_hosted/asyncio_loopback.py
index fd4674544c..03513ae624 100644
--- a/tests/net_hosted/asyncio_loopback.py
+++ b/tests/net_hosted/asyncio_loopback.py
@@ -1,5 +1,12 @@
# Test network loopback behaviour
+import sys
+
+# Only certain platforms can do TCP/IP loopback.
+if sys.platform not in ("darwin", "esp32", "linux"):
+ print("SKIP")
+ raise SystemExit
+
try:
import asyncio
except ImportError: