2804 Commits

Author	SHA1	Message	Date
Damien George	bce854928d	tests/feature_check/tstring.py: Remove check for string.templatelib. ... If a port enables t-strings then it is required to have the `string.templatelib` package (at least to run the tests). That's automatically the case if `MICROPY_PY_TSTRINGS` is enabled. If a port freezes in the micropython-lib `string` extension package then the latest version of this package will include the built-in `string.templatelib` classes. So the feature check for t-strings no longer needs to check if they are available. Signed-off-by: Damien George <damien@micropython.org>	2026-03-24 23:56:05 +11:00
Damien George	6f96d260e6	webassembly/variants/pyscript: Enable weakref module and add tests. ... The webassembly port needs some additional weakref tests due to the fact that garbage collection only happens when Python execution finishes and JavaScript resumes. The `tests/ports/webassembly/heap_expand.py` expected output also needs to be updated because the amount of GC heap got smaller (weakref WTB takes some of the available RAM). Signed-off-by: Damien George <damien@micropython.org>	2026-03-22 23:13:26 +11:00
Damien George	2cca3481f2	tests/basics: Add test for weakref having exception in callback. ... Needs a native exp file because native code doesn't print line numbers in the traceback. Signed-off-by: Damien George <damien@micropython.org>	2026-03-22 23:06:05 +11:00
Damien George	c91d09a00d	tests/basics: Add tests for weakref.ref and weakref.finalize. ... Signed-off-by: Damien George <damien@micropython.org>	2026-03-22 23:06:01 +11:00
Damien George	74e945752b	py/modweakref: Implement weakref module with ref and finalize classes. ... This adds support for the standard `weakref` module, to make weak references to Python objects and have callbacks for when an object is reclaimed by the GC. This feature was requested by PyScript, to allow control over the lifetime of external proxy objects (distinct from JS<->Python proxies). Addresses issue #646 (that's nearly a 12 year old issue!). Functionality added here: - `weakref.ref(object [, callback])` create a simple weak reference with optional callback to be called when the object is reclaimed by the GC - `weakref.finalize(object, callback, /, *args, **kwargs)` create a finalize object that holds a weak reference to an object and allows more convenient callback usage and state change The new module is enabled at the "everything" level. The implementation aims to be as efficient as possible, by adding another bit-per-block to the garbage collector, the WTB (weak table). Similar to the finalizer bit (FTB), if a GC block has its corresponding WTB bit set then a weak reference to that block is held. The details of that weak reference are stored in a global map, `mp_weakref_map`, which maps weak reference to ref/finalize objects, allowing the callbacks to be efficiently found when the object is reclaimed. With this feature enabled the overhead is: - 1/128th of the available memory is used for the new WTB table (eg a 128k heap now needs an extra 1k for the WTB). - Code size is increased. - At garbage collection time, there is a small overhead to check if the collected objects had weak references. This check is the same as the existing FTB finaliser scan, so shouldn't add much overhead. If there are weak reference objects alive (ref/finalize objects) then additional time is taken to call the callbacks and do some accounting to clean up the used weak reference. Signed-off-by: Damien George <damien@micropython.org>	2026-03-22 23:02:38 +11:00
Damien George	406356ec8b	extmod/modlwip: Ensure socket is finalisable if error during creation. ... Because socket objects have a finaliser they must be created carefully, in case an exception is raised during the population of their members, eg invalid input argument or out-of-memory when allocating additional arrays. Prior to the fix in this commit, the finaliser would crash due to `incoming.udp_raw.array` being an invalid pointer in the following cases: - if a SOCK_RAW was created with a proto argument that was not an integer - if a SOCK_DGRAM or SOCK_RAW was created where the allocation of `lwip_incoming_packet_t` failed - if an integer was passed in for the socket type but it was not one of SOCK_STREAM, SOCK_DGRAM or SOCK_RAW Furthermore, if the allocation of `lwip_incoming_packet_t` failed then it may have led to corruption within lwIP when freeing `socket->pcb.raw` because that PCB was not fully set up with its callbacks. This commit fixes all of these issues by ensuring: - `pcb.tcp` and `incoming.udp_raw.array` are initialised to NULL early on - the proto argument is parsed before allocating the PCB - the allocation of `lwip_incoming_packet_t` occurs befor allocating the PCB - `incoming.udp_raw.array` is checked for NULL in the finaliser code The corresponding test (which already checked most of these causes of failure) has been updated to include a previously-uncovered scenario. Signed-off-by: Damien George <damien@micropython.org>	2026-03-21 16:39:40 +11:00
Damien George	8f24c86263	tests/extmod_hardware/machine_pwm.py: Convert test to use target_wiring. ... Signed-off-by: Damien George <damien@micropython.org>	2026-03-20 11:37:15 +11:00
Damien George	142f8b96bf	tests/extmod_hardware/machine_pwm.py: Add pin settings for stm32 port. ... Signed-off-by: Damien George <damien@micropython.org>	2026-03-20 11:37:15 +11:00
Damien George	6e9d35b688	tests/extmod_hardware/machine_pwm.py: Round expected timing calculation. ... To be slightly more accurate computing the expected low/high times for the PWM output. Signed-off-by: Damien George <damien@micropython.org>	2026-03-20 11:37:14 +11:00
Angus Gratton	6cac2d275d	stm32: Add machine.CAN implementation. ... Implemented according to API docs in a parent comment. Adds new multi_extmod/machine_can_* tests which pass when testing between NUCLEO_G474RE, NUCLEO_H723ZG and PYBDV11. This work was mostly funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2026-03-19 17:36:50 +11:00
Angus Gratton	cda49bed27	py/objlist,stm32,esp32: Add helpers for creating/ensuring list args. ... Simplifies the pattern of an optional arg which can be a list of at least a certain length, otherwise one is lazily initialised. Modify pyb.CAN and ESP-NOW APIs to use the helper. Note this changes the return type of pyb.CAN.recv() from tuple to list. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2026-03-19 15:37:19 +11:00
Angus Gratton	bac45e5aaf	tests/ports/stm32/can: Update pyb.CAN tests for FDCAN. ... Also rename the prefix from can to pyb_can, in anticipation of machine.CAN tests. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2026-03-19 09:37:19 +11:00
Andrew Leech	43199278eb	tests/run-tests.py: Ignore known-flaky test failures. ... Reclassify failures of tests listed in flaky_tests_to_ignore as "ignored" instead of retrying them. Ignored tests still run and their output is reported, but they don't affect the exit code. The ci.sh --exclude lists for these tests are removed so they run normally. Signed-off-by: Andrew Leech <andrew.leech@planet-innovation.com>	2026-03-11 14:56:04 +11:00
Koudai Aono	bdef10a92b	tests: Add full feature and coverage tests for PEP 750 template strings. ... Includes corresponding .exp files because this feature is only available in Python 3.14+. Tests for `!a` conversion specifier and space after `!` are not included because they are not supported by MicroPython. Signed-off-by: Koudai Aono <koxudaxi@gmail.com> Signed-off-by: Damien George <damien@micropython.org>	2026-03-09 23:47:33 +11:00
Damien George	d4751a164e	py: Add support for PEP 750's t-strings. ... This commit adds support for t-strings by leveraging the existing f-string parser in the lexer. It includes: - t-string parsing in `py/lexer.c` - new built-in `__template__()` function to construct t-string objects - new built-in `Template` and `Interpolation` classes which implement all the functionality from PEP 750 - new built-in `string` module with `templatelib` sub-module, which contains the classes `Template` and `Interpolation` The way the t-string parser works is that an input t-string like: t"hello {name:5}" is converted character-by-character by the lexer/tokenizer to: __template__(("hello ", "",), name, "name", None, "5") For reference, if it were an f-string it would be converted to: "hello {:5}".format(name) Some properties of this implementation: - it's enabled by default at the full feature level, MICROPY_CONFIG_ROM_LEVEL_AT_LEAST_FULL_FEATURES - when enabled on a Cortex-M bare-metal port it costs about +3000 bytes - there are no limits on the size or complexity of t-strings, and it allows arbitrary levels of nesting of f-strings and t-strings (up to the memory available to the compiler) - the 'a' (ascii) conversion specifier is not supported (MicroPython does not have the built-in `ascii` function) - space after conversion specifier, eg t"{x!r :10}", is not supported - arguments to `__template__` and `Interpolation` are not fully validated (it's not necessary, it won't crash if the wrong arguments are passed in) Otherwise the implementation here matches CPython. Signed-off-by: Damien George <damien@micropython.org>	2026-03-09 23:47:33 +11:00
Damien George	58436b2882	py/lexer: Fix parsing of f'{{'. ... Prior to this fix, f'{{' would raise a SyntaxError. Signed-off-by: Damien George <damien@micropython.org>	2026-03-09 23:14:42 +11:00
Damien George	2322d37a9a	tests/extmod_hardware/machine_counter.py: Separate the connection test. ... Because it requires a different configuration of the pins (in `setUp`). Eg on mimxrt pins used for a `machine.Counter` cannot be read. Signed-off-by: Damien George <damien@micropython.org>	2026-03-09 00:02:04 +11:00
Damien George	43d38d995e	tests/extmod_hardware/machine_encoder.py: Separate the connection test. ... Because it requires a different configuration of the pins (in `setUp`). Eg on mimxrt pins used for an Encoder cannot be read. Signed-off-by: Damien George <damien@micropython.org>	2026-03-09 00:02:04 +11:00
robert-hh	b64f4f9e44	tests/extmod_hardware/machine_encoder.py: Add a MIMXRT configuration. ... For Teensy 4.x. The connectivity tests and the falling edge of the counter test are skipped. Signed-off-by: robert-hh <robert@hammelrath.com>	2026-03-09 00:02:04 +11:00
Damien George	06bfefeaee	py/objstr: Fix b"".hex() so it returns an empty str object. ... As per CPython behaviour, `b"".hex()` should return an empty str object (not an empty bytes object). Fixes issue #18807. Signed-off-by: Damien George <damien@micropython.org>	2026-03-04 12:06:33 +11:00
Damien George	716aae8fb0	tests/basics/builtin_str_hex.py: Remove corresponding .exp file. ... As of CPython 3.7 `bytes.fromhex()` skips all ASCII whitespace. And as of CPython 3.8 `bytes.hex()` supports the optional separator argument. So this test no longer needs a .exp file. Signed-off-by: Damien George <damien@micropython.org>	2026-03-04 12:06:33 +11:00
Angus Gratton	bfc69dbe83	extmod,rp2: Keep LWIP timer running if lwip poll_sockets() is called. ... Fixes rp2 issue where socket.getaddrinfo() could block indefinitely if an interface goes down and still has a DNS server configured, as the LWIP timer stops running and can't time out the DNS query. Adds a regression test under multi_wlan that times out on rp2 without this fix. Fixes issue #18797. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2026-03-04 11:44:30 +11:00
Damien George	95b3e72799	tests/extmod_hardware/machine_pwm.py: Add alif pin config. ... Tested on ALIF_ENSEMBLE and OPENMV_AE3 boards. Signed-off-by: Damien George <damien@micropython.org>	2026-03-04 01:29:35 +11:00
Anson Mansfield	8a1f050771	tests/run-internalbench.py: Add option for running against CPython. ... Occasionally, it's useful to be able to compare MicroPython's performance figures to CPython's. This change adds the ability to run the internalbench test runner with `--test-instance=cpython` in order to execute the same test routines against CPython and produce a benchmark performance report in the same format as MicroPython. Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2026-03-03 23:25:36 +11:00
Angus Gratton	f01373587d	tests/net_inet: Use the letsencrypt TLS root cert for all tests. ... Previously, mpycert.der was the Intermediate certificate which is regularly re-issued by Letsencrypt. Also changes ssl_cert.py to load the cert data from the same file as test_sslcontext_client.py, so the DER string doesn't have to be pasted into the source. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2026-03-03 22:52:23 +11:00
Angus Gratton	0dac591f97	tests/run-multitests.py: Improve error handling for communication error. ... Fixes fatal crash if serial port access returns an error (for example: port is native USB-CDC and the host hard faults during the test run). Instead of crashing, have the runner mark this as a test run error and continue. It's not certain the next test will run successfully, but this provides the context of output showing what was happening when the communication error occurred. Without this change, that output is lost when the fatal exception terminates the runner process. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2026-02-26 19:54:47 +11:00
stijn	e08e3d796c	tests/run-tests.py: Output consistent test file paths. ... Test file paths which get passed to the run_tests function can be absolute or relative and with or without leading slash in the latter case, depending on the arguments to run-tests.py, but since that path is used to: - display which tests run - record which tests ran in the results.json - craft the filename for the .exp/.out file for failed tests it is desirable to always use the same file path irregardless of how the user passed the path. In practice this means that all forms of running our own tests like: >python ./run-tests.py -i extmod >python ./run-tests.py -d extmod >python ./run-tests.py -d ./extmod >python ./run-tests.py -d ../tests/extmod >python ./run-tests.py -d /full/path/to/tests/extmod will now consistently all display the tests like pass extmod/time_time_ns.py FAIL extmod/some_failing_test.py and produce output files like results/extmod_some_failing_test.py.exp results/extmod_some_failing_test.py.out instead of displaying/using the exact path as passed. For external tests, meaning not in the tests/ directory, we also want to be consistent so there the choice was made to always use absolute paths. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	7b9163372d	tests/cmdline: Make tests succeed irregardless of invocation path. ... Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	b8098df3a7	tests/run-tests.py: Use normal discovery if tests dir passed explicitly. ... Scan the --test-dirs argument for the main tests directory being passed and if so do the same thing as if running from within that main test directory. In practice this makes the following (which used to counterintuitively try and fail to run the .py files in the tests/ directory itself) >python micropython/tests/run-tests.py -d micropython/tests do the same thing as >cd micropython/tests >python ./run-tests.py which is logical and convenient. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	ff4d4bfade	tests/run-tests.py: Make skip logic work irregardless of test path. ... Test file paths which get passed to the run_tests function can be absolute or relative and with or without leading slash in the latter case, depending on the arguments to run-tests.py, but the skip_tests list with tests to skip only contains relative paths so using simple string equality comparison easily leads to false negatives. Compare the full absolute path instead such that it doesn't matter anymore in which form the tests are passed. Note: - use realpath to resolve symlinks plus make the comparison case insensitive on windows - the test_file passed to run_one_test is not altered by this commit, such that when the user inputs relative paths the tests are also still displayed with relative paths - likewise the test_file_abspath is not modified because functions like run_micropython rely on it having forward slashes In practice this means that it used to be so that the only forms of running tests for which the skip_tests lists actually worked were: >python ./run-tests.py >python ./run-tests.py -d extmod whereas it now works consistently so also for these invocations, which in the end all point to the exact same path: >python ./run-tests.py -d ./extmod >python ./run-tests.py -d ../tests/extmod >python ./run-tests.py -d /full/path/to/tests/extmod These examples used to not skip any of the tests in the extmod/ directory thereby leading to test failures. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:18:49 +11:00
stijn	2ab88c3d58	tests/run-tests.py: Add an argument for showing which tests would run. ... This is convenient when trying to figure out the correct values for --include/--exclude/--test-dirs/... arguments. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:18:49 +11:00
Jeff Epler	2631b0614c	tests/cpydiff: Add a section for throwing incomplete exceptions. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Jeff Epler	20500558f8	tests/micropython: Add a test for throwing incomplete exception. ... This is a reproducer for #17117. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Damien George	6dbabc9267	tests/extmod/os_urandom.py: Add test for os.urandom. ... Signed-off-by: Damien George <damien@micropython.org>	2026-02-24 23:36:51 +11:00
Alessandro Gatti	43a4914fe1	tests/micropython: Add a test for checking viper value clobbering. ... This commit introduces a test that should check whether viper load or store operations won't clobber either the buffer address or the index value being used. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-24 18:42:53 +11:00
Alessandro Gatti	9dcad25de6	py/emitinlinextensa: Add inline assembler support for windowed cores. ... This commit introduces support for writing inline assembler code snippets when targeting Xtensa cores that use register windows (eg. the whole ESP32 family). Opcodes support is still limited to what the ESP8266 supports (as in, LX3 cores opcodes), however each LX core version is guaranteed to support all previous versions' opcodes as well. The ESP32 does not have the inline assembler enabled by default, following the existing expectations when it comes to firmware footprint. Since now emitted functions may have one of two possible exit sequences, the L32I test had to be fixed. It would return the word containing the L32I opcode itself, but the upper 8 bits of the word came from the following opcode - which can change depending on the exit code sequence. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-07 18:36:22 +11:00
Damien George	ee99014e2a	tests/run-tests.py: Broaden the check for raw REPL failure. ... This is a follow up to 6436f8b93f that catches more cases of a failed raw REPL. If the target device is broken in a certain way then it can have a serial write error instead of just not returning any data. In that case the error raised by `pyboard.py` is "could not enter raw repl: Write timeout", which is slightly different to "could not enter raw repl" (the latter is raised when a serial read fails to return the correct data). The patch here accounts for all cases of a failed raw REPL by using `str.startswith()` instead of a string equality. This can be tested on RPI_PICO_W and RPI_PICO2_W which currently crash in the specific way needed to trigger the write timeout when running the `tests/extmod/socket_badconstructor.py` test. In particular adding the following code to the end of a test (eg `tests/extmod/random_extra.py`) will trigger the issue: import socket try: s = socket.socket(socket.AF_INET, socket.SOCK_RAW, None) except TypeError: pass With the fix here, the `run-tests.py` and `run-natmodtests.py` will abort early if that code is added (prior to the fix they would continue to run all tests and take a long time). Signed-off-by: Damien George <damien@micropython.org>	2026-02-06 13:17:43 +11:00
Damien George	570744d06c	py/runtime: Make import-all support non-modules via __dict__/__all__. ... Prior to this fix, `mp_import_all()` assumed that its argument was exactly a native module instance. That would lead to a crash if something else was passed in, eg a user class via a custom `__import__` implementation or by writing to `sys.modules`. MicroPython already supports injecting non-module objects into the import machinery, so it makes sense to round out that implementation by supporting `from x import *` where `x` is a non-module object. Fixes issue #18639. Signed-off-by: Damien George <damien@micropython.org>	2026-02-05 00:24:14 +11:00
Damien George	7ea88f7da2	py/lexer: Add support for nested f-strings within f-strings. ... It turns out that it's relatively simple to support nested f-strings, which is what this commit implements. The way the MicroPython f-string parser works at the moment is: 1. it extracts the f-string arguments (things in curly braces) into a temporary buffer (a vstr) 2. once the f-string ends (reaches its closing quote) the lexer switches to tokenizing the temporary buffer 3. once the buffer is empty it switches back to the stream. The temporary buffer can easily hold f-strings itself (ie nested f-strings) and they can be re-parsed by the lexer using the same algorithm. The only thing stopping that from working is that the temporary buffer can't be reused for the nested f-string because it's currently being parsed. This commit fixes that by adding a second temporary buffer, which is the "injection" buffer. That allows arbitrary number of nestings with a simple modification to the original algorithm: 1. when an f-string is encountered the string is parsed and its arguments are extracted into `fstring_args` 2. when the f-string finishes, `fstring_args` is inserted into the current position in `inject_chrs` (which is the start of that buffer if no injection is ongoing) 3. `fstring_args` is now cleared and ready for any further f-strings (nested or not) 4. the lexer switches to `inject_chrs` if it's not already reading from it 5. if an f-string appeared inside the f-string then it is in `inject_chrs` and can be processed as before, extracting its arguments into `fstring_args`, which can then be inserted again into `inject_chrs` 6. once `inject_chrs` is exhausted (meaning that all levels of f-strings have been fully processed) the lexer switched back to tokenizing the stream. Amazingly, this scheme supports arbitrary numbers of nestings of f-strings using the same quote style. This adds some code size and a bit more memory usage for the lexer. In particular for a single (non-nested) f-string it now makes an extra copy of the `fstring_args` data, when copying it across to `inject_chrs`. Otherwise, memory use only goes up with the complexity of nested f-strings. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 23:19:09 +11:00
Damien George	617c7dba3b	py/lexer: Use null char as lexer EOF sentinel. ... The null byte cannot exist in source code (per CPython), so use it to indicate the end of the input stream (instead of `(mp_uint_t)-1`). This allows the cache chars (chr0/1/2 and their saved versions) to be 8-bit bytes, making it clear that they are not `unichar` values. It also saves a bit of memory in the `mp_lexer_t` data structure. (And in a future commit allows the saved cache chars to be eliminated entirely by storing them in a vstr instead.) In order to keep code size down, the frequently used `chr0` is still of type `uint32_t`. Having it 32-bit means that machine instructions to load it are smaller (it adds about +80 bytes to Thumb code if `chr0` is changed to `uint8_t`). Also add tests for invalid bytes in the input stream to make sure there are no regressions in this regard. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 23:19:09 +11:00
Damien George	6436f8b93f	tests/run-tests.py: Abort test run if enter_raw_repl fails many times. ... Prior to this change, if a test crashed a board to the point that it was no longer responsive but the serial connection was still alive and able to read/write (eg due to an infinite loop with ctrl-C unavailable), it would take (30 + 10 * number-of-remaining-tests) seconds to finish the test run. That can be 10 minutes or more. The change here aborts the test run if the target does not respond 4 times to when trying to enter the raw REPL at the start of a test. Now, it only takes a maximum of (30 + 4 * 5) = 50 seconds to detect a crashed state and abort the entire test run. Can test this by adding the following to a test: import time, micropython micropython.kbd_intr(-1) while 1: time.sleep(1) For example, add the above to the end of `tests/extmod/random_extra.py` and test via: $ ./run-tests.py -t a0 extmod/[r-z]*.py $ ./run-natmodtests.py -t a0 extmod/[r-z]*.py Previously the `run-tests.py` run would take around 16 minutes. Now it takes under a minute. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 20:17:11 +11:00
Damien George	f624200b31	tests/test_utils.py: Abort test if serial port fails at start. ... All test runners (except `run-multitests.py`) will now abort with error code 2 if the target is a serial port and could not be detected, ie `enter_raw_repl` failed at the detection stage. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 20:17:11 +11:00
Damien George	a1d4f6256c	tests/run-tests.py: Exit with error code 2 if test runner fails. ... The tests runners usually exit with error code 1 when something fails. But it's useful to distinguish between "a test failed" and "the test runner failed". To that end, `run-tests.py` now returns error code 2 when unittest is not installed but is needed. And `run-natmodtests.py` now returns error code 2 when it cannot automatically detect the target architecture. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 20:17:11 +11:00
Damien George	cef2538b10	tests/target_wiring/README: Add README describing target_wiring specs. ... This is now the authoritative place for what should go in a target wiring script. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:59:38 +11:00
Damien George	d291a280bd	tests/target_wiring: Add SPI instance for mimxrt, nrf, renesas-ra, samd. ... Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:59:19 +11:00
Damien George	e5f772ae85	tests/extmod/machine_spi_rate.py: Use target wiring for SPI instances. ... This commit converts `tests/extmod/machine_spi_rate.py` to use the target wiring mechanism, moving the port-specefic definition of the SPI instances that are being tested out of the `tests/extmod/machine_spi_rate.py` file and into the target wiring code. As part of this, the test is changed to always use the default pins for the given SPI instance. This simplifies the test, makes it easier to add support for new ports/boards, and allows reusing the `spi_standalone_args_list` definition in other tests (if needed one day). Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:59:19 +11:00
Damien George	edab53c1da	tests/multi_net: Use random.getrandbits instead of random.randrange. ... The `getrandbits()` function is guaranteed to exist on all ports that have the `random` module (but `randrange()` is not). Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:35:00 +11:00
Damien George	e40d609a0e	tests/multi_net: Skip all ssl/tls tests on axTLS. ... The axTLS implementation of the tls module only has a basic set of features. In particular it doesn't support the CERT_REQUIRED constant nor DTLS, nor can it load the `ec_key.der` key when acting as a server. So skip tests that require these features, which ends up being all the ssl/tls tests. Signed-off-by: Damien George <damien@micropython.org>	2026-02-04 19:35:00 +11:00
Damien George	96bce47762	tests: Factor out common helper functions to separate Python module. ... The test runners have evolved over time and become more and more complex. In particular `tests/run-tests.py` is rather large now. The test runners also duplicate some functionality amongst themselves. As a start to improving this situation, this commit factors out the helper functions from `run-tests.py` into a new `test_utils.py` file, and uses that new module in all test runners. There should be no functional change here. Signed-off-by: Damien George <damien@micropython.org>	2026-01-30 17:03:08 +11:00
Damien George	93692caefa	extmod/modmarshal: Support marshal.dumps of functions with children. ... This commit adds support to the `marshal` module to be able to dump functions that have child functions. For example: import marshal def f(): def child(): return 1 return child marshal.dumps(f.__code__) It also covers the case of marshalling functions that use list comprehensions, because a list comprehension uses a child function. This is made possible by the newly enhanced `mp_raw_code_save_fun_to_bytes()` that can now handle nested functions. Unmarshalling via `marshal.loads()` already supports nested functions because it uses the standard `mp_raw_code_load_mem()` function which is used to import mpy files (and hence can handle all possibilities). Signed-off-by: Damien George <damien@micropython.org>	2026-01-27 01:20:36 +11:00