diff options
| author | Damien George <damien@micropython.org> | 2025-07-17 15:28:15 +1000 |
|---|---|---|
| committer | Damien George <damien@micropython.org> | 2025-07-23 12:42:44 +1000 |
| commit | 941b7e35acd8bd7597ba6a6111cb8e94662094b5 (patch) | |
| tree | 9ffcb2dc97bcaf5469c005803af8bdc60143fb3b | |
| parent | cc774c3daf68f3e2e1e920d7728b3c07cf6da32e (diff) | |
tests/run-tests.py: Use TEST_TIMEOUT as timeout for bare-metal tests.
This parameter is already used for PC-based tests (eg unix and webassembly
ports), and it makes sense for it to be used for bare-metal ports as well.
That way the timeout is configurable for all targets.
Because this increases the default timeout from 10s to 30s, this fixes some
long-running tests that would previously fail due to a timeout such as
`thread/stress_aes.py` on ESP32.
Signed-off-by: Damien George <damien@micropython.org>
| -rwxr-xr-x | tests/run-tests.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/run-tests.py b/tests/run-tests.py index e2e95884a..522027c1f 100755 --- a/tests/run-tests.py +++ b/tests/run-tests.py @@ -15,7 +15,7 @@ from multiprocessing.pool import ThreadPool import threading import tempfile -# Maximum time to run a PC-based test, in seconds. +# Maximum time to run a single test, in seconds. TEST_TIMEOUT = float(os.environ.get('MICROPY_TEST_TIMEOUT', 30)) # See stackoverflow.com/questions/2632199: __file__ nor sys.argv[0] @@ -333,7 +333,7 @@ def run_script_on_remote_target(pyb, args, test_file, is_special): try: had_crash = False pyb.enter_raw_repl() - output_mupy = pyb.exec_(script) + output_mupy = pyb.exec_(script, timeout=TEST_TIMEOUT) except pyboard.PyboardError as e: had_crash = True if not is_special and e.args[0] == "exception": |