kopia lustrzana https://github.com/micropython/micropython
7ec95c2768
Currently when using uasyncio.start_server() the socket configuration is done inside a uasyncio.create_task() background function. If the address and port are already in use however this throws an OSError which cannot be cleanly caught behind the create_task(). This commit moves the getaddrinfo and socket binding to the start_server() function, and only creates the task if that succeeds. This means that any OSError from the initial socket configuration is propagated directly up the call stack, compatible with CPython behaviour. See #7444. Signed-off-by: Damien George <damien@micropython.org> |
||
|---|---|---|
| .. | ||
| basics | ||
| cmdline | ||
| cpydiff | ||
| esp32 | ||
| extmod | ||
| feature_check | ||
| float | ||
| import | ||
| inlineasm | ||
| internal_bench | ||
| io | ||
| jni | ||
| micropython | ||
| misc | ||
| multi_bluetooth | ||
| multi_net | ||
| net_hosted | ||
| net_inet | ||
| perf_bench | ||
| pyb | ||
| pybnative | ||
| qemu-arm | ||
| stress | ||
| thread | ||
| unicode | ||
| unix | ||
| wipy | ||
| README | ||
| run-internalbench.py | ||
| run-multitests.py | ||
| run-natmodtests.py | ||
| run-perfbench.py | ||
| run-tests-exp.py | ||
| run-tests-exp.sh | ||
| run-tests.py | ||
README
This directory contains tests for various functionality areas of MicroPython. To run all stable tests, run "run-tests.py" script in this directory. Tests of capabilities not supported on all platforms should be written to check for the capability being present. If it is not, the test should merely output 'SKIP' followed by the line terminator, and call sys.exit() to raise SystemExit, instead of attempting to test the missing capability. The testing framework (run-tests.py in this directory, test_main.c in qemu_arm) recognizes this as a skipped test. There are a few features for which this mechanism cannot be used to condition a test. The run-tests.py script uses small scripts in the feature_check directory to check whether each such feature is present, and skips the relevant tests if not. Tests are generally verified by running the test both in MicroPython and in CPython and comparing the outputs. If the output differs the test fails and the outputs are saved in a .out and a .exp file respectively. For tests that cannot be run in CPython, for example because they use the machine module, a .exp file can be provided next to the test's .py file. A convenient way to generate that is to run the test, let it fail (because CPython cannot run it) and then copy the .out file (but not before checking it manually!) When creating new tests, anything that relies on float support should go in the float/ subdirectory. Anything that relies on import x, where x is not a built-in module, should go in the import/ subdirectory.