2447 Commits

Author	SHA1	Message	Date
Damien George	2c80d36998	tests/extmod: Convert machine1.py test to use unittest. ... Signed-off-by: Damien George <damien@micropython.org>	2024-12-06 13:48:23 +11:00
Damien George	c7c3ffa45f	tests/net_hosted: Convert connect-nonblock-xfer test to use unittest. ... This allows it to run parts of the test on esp8266 (or any target using axTLS). Signed-off-by: Damien George <damien@micropython.org>	2024-12-06 13:48:23 +11:00
Damien George	f62df1a2c2	tests/ports/stm32_hardware: Convert DMA test to use unittest. ... Signed-off-by: Damien George <damien@micropython.org>	2024-12-06 13:48:23 +11:00
Damien George	a8422439ab	tests/run-tests.py: Print .out file when there is no .exp file. ... So that a failing unittest-based test has its entire log printed when using `run-tests.py --print-failures`. Signed-off-by: Damien George <damien@micropython.org>	2024-12-06 13:47:21 +11:00
Damien George	a2554f0957	tests/run-tests.py: Add support for tests to use unittest. ... All the existing tests require a .exp file (either manually specified or generated running the test first under CPython) that is used to check the output of running the test under MicroPython. The test passes if the output matches the expected output exactly. This has worked very well for a long time now. But some of the newer hardware tests (eg UART, SPI, PWM) don't really fit this model, for the following main reasons: - Some but not all parts of the test should be skipped on certain hardware targets. With the expected-output approach, skipping tests is either all or nothing. - It's often useful to output diagnostics as part of the test, which should not affect the result of the test (eg the diagnostics change from run to run, like timing values, or from target to target). - Sometimes a test will do a complex check and then print False/True if it passed or not, which obscures the actual test result. To improve upon this, this commit adds support to `run-tests.py` for a test to use `unittest`. It detects this by looking at the end of the output after running the test, looking for the test summary printed by `unittest` (or an error message saying `unittest` was not found). If the test uses `unittest` then it should not have a .exp file, and it's not run under CPython. A `unittest` based test passes or fails based on the summary printed by `unittest`. Note that (as long as `unittest` is installed on the target) the tests are still fully independent and you can still run them without `run-tests.py`: you just run it as usual, eg `mpremote run <test.py>`. This is very useful when creating and debugging tests. Note also that the standard test suite testing Python semantics (eg everything in `tests/basics/`) will probably never use unittest. Only more advanced tests will, and ones that are not runnable under CPython. Signed-off-by: Damien George <damien@micropython.org>	2024-12-06 13:41:52 +11:00
Angus Gratton	eb80b04944	tests/extmod: Workaround CPython warning in asyncio_new_event_loop test. ... This started failing in CI on the mingw build, after CPython updated to 3.12.7. The test prints two warnings during interpreter shutdown of "Task was destroyed but it is pending!". This didn't happen on other CPython builds, and I think that's because of finalizer order in CPython interpreter shutdown but not certain (the loop finalizer calls loop.close() if not already closed). Adding explicit calls to loop.close() causes the warning to be printed on every run with CPython 3.12.7 on Linux. Next, added the workaround exception handler to swallow this exception as MicroPython doesn't produce an equivalent. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-11-28 23:12:34 +11:00
Angus Gratton	8e11e5f1a1	tests/misc/sys_settrace_features.py: Add note about CPython 3.12 issue. ... CPython 3.12 has a documented issue with settrace for opcodes, apparently due to PEP 669. "This behavior will be changed back in 3.13 to be consistent with previous versions." No easy way to make the test pass on CPython 3.12, but at least this helps signal what the problem is to anyone who runs into a failure. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-11-28 23:11:36 +11:00
Corran Webster	e70048cf59	extmod/modframebuf: Fix 0 radius bug in FrameBuffer.ellipse. ... This fixes a bug in FrameBuffer.ellipse where it goes into an infinite loop if both radii are 0. This fixes the bug with a simple pre-check to see if both radii are 0, and in that case sets a single pixel at the center. This is consistent with the behaviour of the method when called with just one of the radii set to 0, where it will draw a horizontal or vertical line of 1 pixel width. The pixel is set with setpixel_checked so it should handle out-of-bounds drawing correctly. This fix also includes three new tests: one for the default behaviour, one for drawing out-of-bounds, and one for when the sector mask is 0. Fixes issue #16053. Signed-off-by: Corran Webster <cwebster@unital.dev>	2024-11-28 22:56:44 +11:00
Angus Gratton	0e383a31b9	tests: Add basic wlan test. ... Includes adding some ESP8266 port output to the ignored output list for the multitest runner. This test passes on ESP8266 and various ESP32s (including talking to each other). Without the fix in the parent commit, ESP32 AP will fail if the station can report its channel (i.e. channel is wrong). Testing with a CYW43 (RPI_PICO_W) currently fails but I have some fixes to submit so it can pass as well. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-11-28 15:39:06 +11:00
Angus Gratton	7647c828de	tests/multi_espnow: Add channel setting test, add some docs. ... Test currently passes. It was added so it can be used to check for regressions when fixing channel selection for AP mode in a follow-up commit. Also add some docs about how channel setting is observed to work for ESP-NOW. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-11-28 15:39:06 +11:00
Damien George	69023622ee	tests/net_hosted: Improve and simplify non-block-xfer test. ... CPython changed its non-blocking socket behaviour recently and this test would not run under CPython anymore. So the following steps were taken to get the test working again and then simplify it: - Run the test against CPython 3.10.10 and capture the output into the .exp file for the test. - Run this test on unix port of MicroPython and verify that the output matches the CPython 3.10.10 output in the new .exp file (it did). From now on take unix MicroPython as the source of truth for this test when modifying it. - Remove all code that was there for CPython compatibility. - Make it print out more useful information during the test run, including names of the OSError errno values. - Add polling of the socket before the send/write/recv/read to verify that the poll gives the correct result in non-blocking mode. Tested on unix MicroPython, ESP32_GENERIC, PYBD_SF2 and RPI_PICO_W boards. Signed-off-by: Damien George <damien@micropython.org>	2024-11-13 11:44:09 +11:00
Jeff Epler	3844733d60	tests/cpydiff: Fix test case for modules_json_nonserializable. ... The test case was producing the following error: Traceback (most recent call last): File "<stdin>", line 12, in <module> UnicodeError: which did not demonstrate the intended difference (this particular non-json-serializable object DID throw an exception! just not TypeError). The updated test uses a byte string with all ASCII bytes inside, which better illustrates the diference. Signed-off-by: Jeff Epler <jepler@gmail.com>	2024-11-11 12:35:03 +11:00
Angus Gratton	5dfbd43714	tests: Use the recommended network.WLAN.IF_[AP|STA] constants. ... Removes the deprecated network.[AP|STA]_IF form from unit tests. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-11-08 12:03:50 +11:00
Damien George	85053adb24	tests/run-tests.py: Add mimxrt and samd platforms. ... Signed-off-by: Damien George <damien@micropython.org>	2024-11-04 12:48:10 +11:00
Damien George	8978102f35	tests/run-tests.py: Change --target/--device options to --test-instance. ... Previously to this commit, running the test suite on a bare-metal board required specifying the target (really platform) and device, eg: $ ./run-tests.py --target pyboard --device /dev/ttyACM1 That's quite a lot to type, and you also need to know what the target platform is, when a lot of the time you either don't care or it doesn't matter. This commit makes it easier to run the tests by replacing both of these options with a single `--test-instance` (`-t` for short) option. That option specifies the executable/port/device to test. Then the target platform is automatically detected. The `--test-instance` can be passed: - "unix" (the default) to use the unix version of MicroPython - "webassembly" to test the webassembly port - anything else is considered a port/device to pass to Pyboard There are also some shortcuts to specify a port/device, following `mpremote`: - a<n> is short for /dev/ttyACM<n> - u<n> is short for /dev/ttyUSB<n> - c<n> is short for COM<n> For example: $ ./run-tests.py -t a1 Note that the default test instance is "unix" and so this commit does not change the standard way to run tests on the unix port, by just doing `./run-tests.py`. As part of this change, the platform (and it's native architecture if it supports importing native .mpy files) is show at the start of the test run. Signed-off-by: Damien George <damien@micropython.org>	2024-11-04 12:47:47 +11:00
Damien George	f2ac471989	tests/run-tests.py: Simplify the way target-specific tests are given. ... Signed-off-by: Damien George <damien@micropython.org>	2024-11-04 12:02:55 +11:00
Damien George	c88a9d60a1	tests/basics/deque2.py: Add tests for deque subscript-from-end. ... Signed-off-by: Damien George <damien@micropython.org>	2024-11-04 11:22:43 +11:00
Damien George	09ea901317	tests/extmod: Add test to compare time_ns with time. ... They should be close together. Signed-off-by: Damien George <damien@micropython.org>	2024-10-24 23:24:09 +11:00
Damien George	1ec0c9b886	tests/extmod: Use time_ns instead of time in lfs mtime test. ... Because VfsLfs2 uses time_ns to create timestamps for files, and for the test to give consistent results it also needs to use this same function. Signed-off-by: Damien George <damien@micropython.org>	2024-10-24 23:24:09 +11:00
Damien George	ca6aed7649	tests/extmod: Fix access of RTC class in machine.RTC test. ... This previously passed on some targets that automatically import the `machine` module in `boot.py`. Signed-off-by: Damien George <damien@micropython.org>	2024-10-24 16:29:43 +11:00
Damien George	6d98280fda	tests/extmod: Add a simple test for machine.RTC. ... Tests at least that the datetime can be set and get correctly. Signed-off-by: Damien George <damien@micropython.org>	2024-10-24 11:43:03 +11:00
Damien George	3f54e5dff2	tests/extmod: Support esp32,mimxrt,stm32,samd ports in UART TX test. ... Getting this test running on stm32- and mimxrt-based boards requires adding a small delay after constructing the UART so that the initial idle frame has time to be transmitted before the test starts. Also, the timing margin needs to account for an additional 1-bit worth of time on some MCUs. Thanks to @robert-hh for the esp32, mimxrt and samd settings. Signed-off-by: Damien George <damien@micropython.org>	2024-10-22 22:21:17 +11:00
Damien George	0646177997	tests/extmod: Make invalid-blockdev test work consistently on all ports. ... Some ports (eg stm32) configure the FAT driver differently (eg with multi-partition support) and that leads to a slightly different sequence of block reads, compared to other configurations (eg rp2). Comment out the printing in `readblocks()` so the tests are deterministic (the printing is still useful for debugging). Signed-off-by: Damien George <damien@micropython.org>	2024-10-22 14:32:51 +11:00
Damien George	f7abb52847	tests/run-tests.py: Skip large viper test on esp8266. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-22 14:31:13 +11:00
Damien George	52f2ba5677	tests/micropython: Tweak ringio test for targets with terse errors. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-22 14:31:13 +11:00
Damien George	1e3b24238e	tests/extmod: Adjust ssl/tls tests to run on targets with axTLS. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-22 14:31:13 +11:00
Damien George	7d442373af	tests/extmod: Config SPI test for esp8266 and skip SoftTimer test. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-22 14:31:13 +11:00
Corran Webster	d1574de3b6	extmod/modframebuf: Fix FrameBuffer size check for stride corner-cases. ... This is a fix for issue #15944, and handles corner cases in the FrameBuffer code when using stride values where the last line's stride may extend past the end of the underlying buffer. This commit includes extra tests for these corner cases. For example a GS8 format FrameBuffer with a width of 8, height of 2 and stride of 10 should be able to fit into a buffer of size 18 (10 bytes for the first horizontal line, and 8 bytes for the second -- the full 10 bytes are not needed). Similarly a 1 by 9 FrameBuffer in MONO_VLSB format with a stride of 10 should be able to fit into a buffer of length 11 (10 bytes for the first 8 lines, and then one byte for the 9th line. Being able to do this is particularly important when cropping the corner of an existing FrameBuffer, either to copy a sprite or to clip drawing. Signed-off-by: Corran Webster <cwebster@unital.dev>	2024-10-22 13:05:31 +11:00
Damien George	97af1001ae	rp2/machine_uart: Make it so TX is done only when no longer busy. ... Prior to this commit, when flushing a UART on the rp2 port, it returns just before the last character is sent out the wire. Fix this by waiting until the BUSY flag is cleared. This also fixes the behaviour of `UART.txdone()` to return `True` only when the last byte has gone out. Updated docs and tests to match. The test now checks that UART TX time is very close to the expected time (prior, it was just testing that the TX time was less than the expected time). Signed-off-by: Damien George <damien@micropython.org>	2024-10-22 10:17:05 +11:00
Damien George	1b89c503db	py/objtype: Don't delegate lookup of descriptor methods to __getattr__. ... When descriptors are enabled, lookup of the `__get__`, `__set__` and `__delete__` descriptor methods should not be delegated to `__getattr__`. That follows CPython behaviour. Signed-off-by: Damien George <damien@micropython.org>	2024-10-16 15:03:30 +11:00
Damien George	b33f64792f	tests/run-tests.py: Only run inlineasm tests on rp2 ARM targets. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-15 12:23:06 +11:00
Damien George	b42bb911c6	tests/ports/rp2: Update lightsleep/machine_idle to skip on RP2350. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-15 12:23:06 +11:00
Damien George	651b63cd79	tests/ports/rp2: Add simple rp2-specific UART test. ... To test construction of UART instances. Signed-off-by: Damien George <damien@micropython.org>	2024-10-15 12:23:06 +11:00
Damien George	fda7ae83a8	tests/ports/rp2: Update DMA test to work on RP2350. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-15 12:21:10 +11:00
Damien George	7746785035	tests/run-tests.py: Wait for soft reset if a target skips a test. ... Commit 69c25ea865 made raising `SystemExit` do a soft reset (on bare-metal targets). This means that any test which is skipped by a target (by raising `SystemExit`) will trigger a soft reset on that target, and then it must execute its startup code, such as `boot.py`. If the timing is right, this startup code can be unintentionally interrupted by the test runner when preparing the next test, because the test runner enters the raw REPL again via a Ctrl-C Ctrl-A ctrl-D sequence (in `Pyboard.enter_raw_repl()`). When this happens (`boot.py` is interrupted) the target may not be set up correctly, and it may (in the case of stm32 boards) flash LEDs and take extra time, slowing down the test run. Fix this by explicitly waiting for the target to finish its soft reset when it skips a test. Signed-off-by: Damien George <damien@micropython.org>	2024-10-15 11:23:07 +11:00
Angus Gratton	05ac69329d	esp32: Fix hang in taskYIELD() on riscv CPUs when IRQs disabled. ... Regression introduced in 337742f. The hang occurs because the esp32 port was calling "from ISR" port-layer functions to set/clear the interrupt mask. FreeRTOS kernel therefore doesn't know the CPU is in a critical section. In taskYIELD() the riscv port layer blocks after yielding until it knows the yield has happened, and would block indefinitely if IRQs are disabled (until INT WDT triggers). Moving to the "public" portENTER_CRITICAL/portEXIT_CRITICAL API means that FreeRTOS knows we're in a critical section and can react accordingly. Adds a regression test for this case (should be safe to run on all ports). On single core CPUs, this should result in almost exactly the same behaviour apart from fixing this case. On dual core CPUs, we now have cross-CPU mutual exclusion for atomic sections. This also shouldn't change anything, mostly because all the code which enters an atomic section runs on the same CPU. If it does change something, it will be to fix a thread safety bug. There is some risk that this change triggers a FreeRTOS crash where there is a call to a blocking FreeRTOS API with interrupts disabled. Previously this code might have worked, but was probably thread unsafe and would have hung in some circumstances. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-10-10 10:59:51 +11:00
Damien George	197becbdcc	tests: Tweak machine SPI and UART tests to work with esp32c6. ... Signed-off-by: Damien George <damien@micropython.org>	2024-10-09 23:34:27 +11:00
Andrew Leech	c2eebe0609	tests/README: Update instructions for key/cert pair usage on device. ... Signed-off-by: Andrew Leech <andrew@alelec.net>	2024-10-09 14:37:59 +11:00
stijn	338df1ae35	py/objtype: Allow passing keyword arguments to native base __init__. ... Allowing passing keyword arguments to a native base's __init__, i.e. `make_new` in the C code. Previously only positional arguments were allowed. The main trade-off in this commit is that every call to the native base's `make_new` is now going to be preceded by a call to `mp_map_init_fixed_table` even though most of what that does is unused and instead it merely serves as a way to pass the number of keyword arguments. Fixes issue #15465. Signed-off-by: stijn <stijn@ignitron.net>	2024-10-07 11:37:52 +11:00
Alessandro Gatti	43b05afdf5	py/mpz: Skip separators when running out of digits to print. ... This commit fixes the addition of a stray separator before the number when printing an MPZ-backed integer and the first group is three digits long. This fixes #8984. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2024-09-26 23:39:06 +10:00
Damien George	5b22bde044	py/persistentcode: Explicitly track native BSS/rodata when needed. ... Signed-off-by: Damien George <damien@micropython.org>	2024-09-26 22:15:28 +10:00
Angus Gratton	f4ab9d9247	extmod/vfs_blockdev: Implement common helper for read and write. ... - Code size saving as all of these functions are very similar. - Resolves the "TODO" of the plain read and write functions not propagating errors. An error in the underlying block device now causes VFatFs to return EIO, for example. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-09-26 22:08:48 +10:00
Angus Gratton	4f6d4b2b49	extmod/vfs_blockdev: Check block device function positive results. ... A positive result here can result in eventual memory corruption as littlefs expects the result of a cache read/write function to be 0 or a negative integer for an error. Closes #13046 This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-09-26 22:08:48 +10:00
Andrew Leech	7e14680a83	py/objringio: Add micropython.RingIO() interface for general use. ... This commit adds a new `RingIO` type which exposes the internal ring-buffer code for general use in Python programs. It has the stream interface making it similar to `StringIO` and `BytesIO`, except `RingIO` has a fixed buffer size and is automatically safe when reads and writes are in different threads or an IRQ. This new type is enabled at the "extra features" ROM level. Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2024-09-19 18:00:44 +10:00
Michael Sawyer	230e521515	tests/ports/unix: Update and extend the modffi integer tests. ... Added the "long" modffi tests. The tests could not be added to the existing ffi_types test because two .exp files were required for the 32-bit and 64-bit results. Code common to both the ffi_types and type "long" tests was factored into ffi_int_base. ffi_types was renamed to ffi_int_types to group the related tests under the "ffi_int" prefix. Signed-off-by: Michael Sawyer <mjfsawyer@gmail.com>	2024-09-19 15:00:17 +10:00
Damien George	1be38e8077	tests/run-tests.py: Remove --write-exp and --list-tests options. ... Removing the now-unused (see previous commit for details) `--write-exp` and `--list-tests` options helps to simplify the rather complex logic in `run-tests.py`. Signed-off-by: Damien George <damien@micropython.org>	2024-09-19 13:36:04 +10:00
Angus Gratton	5d8878b582	shared/tinyusb: Only run TinyUSB on the main thread if GIL is disabled. ... If GIL is disabled then there's threat of a race condition if some other code specifically requests USB processing (i.e. to unblock stdio), while a scheduled TinyUSB callback is already running on another thread. Relies on the change in the parent commit, where scheduler is restricted to main thread if GIL is disabled. Fixes #15390 - "TinyUSB callback can't recurse" exceptions on rp2 when using _thread module and USB serial I/O. Adds a unit test for stdin functioning correctly in threads (fails on rp2 port without this fix). This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-09-19 13:17:01 +10:00
Damien George	74d6dba294	tests/run-tests.py: Add a zephyr test target. ... So that certain tests can be skipped when running on this target. These thread tests do not pass because the zephyr port cannot create more than 4 threads at once. Signed-off-by: Damien George <damien@micropython.org>	2024-09-06 20:47:19 +10:00
danicampora	935fcd1329	tests/thread: Adapt stress_aes.py to run on zephyr. ... Signed-off-by: danicampora <danicampora@gmail.com>	2024-09-06 20:42:57 +10:00
robert-hh	e23fdb1f77	tests/extmod/machine_uart_irq_txidle.py: Simplify the test script. ... Now that no minimal delay time is required for SAMD devices. Signed-off-by: robert-hh <robert@hammelrath.com>	2024-09-06 17:43:49 +10:00