109 Commits

Author	SHA1	Message	Date
Damien George	1401fdb8b3	tests/run-tests.py: Run tests-with-regex-output as normal tests. ... Some tests (currently given by the `special_tests` list) have output which must be mached via a regex, because it can change from run to run (eg the address of an object is printed). These tests are currently classified as `is_special` in the test runner, which means they get special treatment. In particular they don't set the emitter as specified by `args.emit`. That means these tests do not run via .mpy or using the native emitter, even if those options are given on the command line. This commit fixes that by considering `is_special` as different to `tests_with_regex_output`. The former is used for things like target feature detection (which are not really tests) and when extra command line options need to be passed to the unix micropython executable. The latter (now called `tests_with_regex_output`) are specifically for tests that have output to be matched via regex. The `thread_exc2.py` test now needs to be excluded when running using the native emitter, because the native emitter doesn't print traceback info. And the `sys_settrace_cov.py` test needs to be excluded because set-trace output is different with the native emitter. Signed-off-by: Damien George <damien@micropython.org>	2025-08-10 11:40:54 +10:00
Damien George	c35427cbdb	tests/run-tests.py: Move tests to skip with native emitter to a list. ... This makes `run-tests.py` a little more organised, by putting all the tests-to-skip-when-using-the-native-emitter in a dedicated list. This should make it easier to maintain the list, and understand why a test is there. Signed-off-by: Damien George <damien@micropython.org>	2025-08-10 11:25:38 +10:00
Yoctopuce dev	dbbaa959c8	py/formatfloat: Improve accuracy of float formatting code. ... Following discussions in PR #16666, this commit updates the float formatting code to improve the `repr` reversibility, i.e. the percentage of valid floating point numbers that do parse back to the same number when formatted by `repr` (in CPython it's 100%). This new code offers a choice of 3 float conversion methods, depending on the desired tradeoff between code size and conversion precision: - BASIC method is the smallest code footprint - APPROX method uses an iterative method to approximate the exact representation, which is a bit slower but but does not have a big impact on code size. It provides `repr` reversibility on >99.8% of the cases in double precision, and on >98.5% in single precision (except with REPR_C, where reversibility is 100% as the last two bits are not taken into account). - EXACT method uses higher-precision floats during conversion, which provides perfect results but has a higher impact on code size. It is faster than APPROX method, and faster than the CPython equivalent implementation. It is however not available on all compilers when using FLOAT_IMPL_DOUBLE. Here is the table comparing the impact of the three conversion methods on code footprint on PYBV10 (using single-precision floats) and reversibility rate for both single-precision and double-precision floats. The table includes current situation as a baseline for the comparison: PYBV10 REPR_C FLOAT DOUBLE current = 364688 12.9% 27.6% 37.9% basic = 364812 85.6% 60.5% 85.7% approx = 365080 100.0% 98.5% 99.8% exact = 366408 100.0% 100.0% 100.0% Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-08-01 00:47:33 +10:00
Anson Mansfield	88cb6bc818	tests/run-internalbench.py: Allow running internalbench on hardware. ... Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2025-07-29 11:49:10 +10:00
Damien George	7729e80fdd	all: Go back to using default ruff quote style. ... Commit dc2fcfcc55 seems to have accidentally changed the ruff quote style to "preserve", instead of keeping it at the default which is "double". Put it back to the default and update relevant .py files with this rule. Signed-off-by: Damien George <damien@micropython.org>	2025-07-24 12:48:18 +10:00
Yoctopuce dev	d6876e2273	py/obj: Fix REPR_C bias toward zero. ... Current implementation of REPR_C works by clearing the two lower bits of the mantissa to zero. As this happens after each floating point operation, this tends to bias floating point numbers towards zero, causing decimals like .9997 instead of rounded numbers. This is visible in test cases involving repeated computations, such as `tests/misc/rge_sm.py` for instance. The suggested fix fills in the missing bits by copying the previous two bits. Although this cannot recreate missing information, it fixes the bias by inserting plausible values for the lost bits, at a relatively low cost. Some float tests involving irrational numbers have to be softened in case of REPR_C, as the 30 bits are not always enough to fulfill the expectations of the original test, and the change may randomly affect the last digits. Such cases have been made explicit by testing for REPR_C or by adding a clear comment. The perf_test fft code was also missing a call to round() before casting a log_2 operation to int, which was causing a failure due to a last-decimal change. Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-07-24 11:07:30 +10:00
Damien George	941b7e35ac	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>	2025-07-23 12:42:44 +10:00
Damien George	167c888df9	tests/run-tests.py: Detect threading and automatically run thread tests. ... When detecting the target platform, also check if it has threading and whether the GIL is enabled or not (using the new attribute `sys.implementation._thread`). If threading is available, add the thread tests to the set of tests to run (unless the set of tests is explicitly given). With this change, the unix port no longer needs to explicitly run the set of thread tests, so that line has been removed from the Makefile. This change will make sure thread tests are run with other testing combinations. In particular, thread tests are now run: - on the unix port with the native emitter - on macOS builds - on unix qemu, the architectures MIPS, ARM and RISCV-64 Signed-off-by: Damien George <damien@micropython.org>	2025-07-23 11:06:09 +10:00
Angus Gratton	2d8d64059f	tests: Add specific tests for "long long" 64-bit bigints. ... These will run on all ports which support them, but importantly they'll also run on ports that don't support arbitrary precision but do support 64-bit long ints. Includes some test workarounds to account for things which will overflow once "long long" big integers overflow (added in follow-up commit): - uctypes_array_load_store test was failing already, now won't parse. - all the ffi_int tests contain 64-bit unsigned values, that won't parse as long long. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-07-18 00:10:44 +10:00
Jim Mussared	5e9189d6d1	py/vm: Avoid heap-allocating slices when subscripting built-ins. ... This commit adds a fast-path optimisation for when a BUILD_SLICE is immediately followed by a LOAD/STORE_SUBSCR for a native type, to avoid needing to allocate the slice on the heap. In some cases (e.g. `a[1:3] = x`) this can result in no allocations at all. We can't do this for instance types because the get/set/delattr implementation may keep a reference to the slice. Adds more tests to the basic slice tests to ensure that a stack-allocated slice never makes it to Python, and also a heapalloc test that verifies (when using bytecode) that assigning to a slice is no-alloc. This work was funded through GitHub Sponsors. Signed-off-by: Jim Mussared <jim.mussared@gmail.com> Signed-off-by: Damien George <damien@micropython.org>	2025-07-16 00:12:47 +10:00
Damien George	8f8f853982	tests/run-tests.py: Consider tests ending in _async.py as async tests. ... The test `micropython/ringio_async.py` is a test that requires async keyword support, and will fail with SyntaxError on targets that don't support async/await. Really it should be skipped on such targets, and this commit makes sure that's the case. Signed-off-by: Damien George <damien@micropython.org>	2025-07-12 23:48:17 +10:00
Jeff Epler	a8c2b917e2	tools/ci.sh: Increase test timeout to 60s in coverage jobs. ... The additional overhead of the settrace profiler means that the `aes_stress.py` test was running too slowly on GitHub CI. Double the timeout to 60 seconds. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-07-06 00:08:13 +10:00
Jeff Epler	ff8c4e5943	tests/misc: Improve test coverage of py/profile.c. ... Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-07-06 00:05:36 +10:00
Alessandro Gatti	6fd7422a8e	tests/run-tests.py: Allow injected code customisation. ... This commit introduces a mechanism to customise the code that is injected to the board when performing a test file upload and execution. A new argument, --begin", is added so regular Python code can be inserted in the injected fragment between the module file creation and the effective file import. This is needed for running larger tests (usually ones that have been pre-compiled with "--via-mpy --emit native") on ESP8266, as that board does not have enough memory to fit certain blocks of code unless additional configuration is performed. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-07-01 15:43:17 +10:00
Andrew Leech	5e965618be	tests/run-tests.py: Add support for ctrl keys in REPL tests. ... This allows having {\xDD} in tests, which will be expanded to the given hex character. Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-06-19 17:23:39 +10:00
Damien George	2bc5af6945	tests/run-tests.py: Factor out helper function to create test report. ... This commit factors existing code in `run-tests.py` into a new helper function `create_test_report()`. That function prints out a summary of the test run (eg number of tests passed, number failed, number skipped) and creates the corresponding `_results.json` file. This is done so `create_test_report()` can be reused by the other test runners. The `test_count` counter is now gone, and instead the number of passed plus number of failed tests is used as an equivalent count. For consistency this commit makes a minor change to the printed output of `run-tests.py`: instead of printing a shorthand name for tests that failed or skipped, it now prints the full name. Eg what was previously printed as `attrtuple2` is now printed as `basics/attrtuple2.py`. This makes the output a little longer (when there are failed/skipped tests) but helps to disambiguate the test name, eg which directory it's in. Signed-off-by: Damien George <damien@micropython.org>	2025-06-12 21:47:20 +10:00
Alessandro Gatti	c1c73d966e	tests/run-tests.py: Unconditionally enable native tests if asked. ... This commit lets the test runner enumerate and run native tests if the feature check fails but native tests were explicitly requested from the command line. The old behaviour would disable native tests anyway if the feature check failed, however this hid a bug in the x86 native emitter that would be triggered even during the feature check. That meant the test suite would pass on x86 even with a broken emitter, as those tests would have been skipped anyway. Now, if the user asks for native code it will get native code out of the runner no matter what. Co-authored-by: Damien George <damien@micropython.org> Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-10 11:29:02 +10:00
Damien George	5b340b12b8	tests/run-tests.py: Remove filename arg from prepare_script_for_target. ... It's no longer used. Signed-off-by: Damien George <damien@micropython.org>	2025-06-05 15:18:30 +10:00
Damien George	229104558f	tests/run-tests.py: Automatically skip tests that are too large. ... Some tests are just too big for targets that don't have much heap memory, eg `tests/extmod/vfs_rom.py`. Other tests are too large because the target doesn't have enough IRAM for native code, eg esp8266 running `tests/micropython/viper_args.py`. Previously, such tests were explicitly skipped on targets known to have little memory, eg esp8266. But this doesn't scale to multiple targets, nor to more and more tests which are too large. This commit addresses that by adding logic to the test runner so it can automatically skip tests when they don't fit in the target's memory. It does this by prepending a `print('START TEST')` to every test, and if a `MemoryError` occurs before that line is printed then the test was too big. This works for standard tests, tests that go via .mpy files, and tests that run in native emitter mode via .mpy files. For tests that are too big, it prints `lrge <test name>` on the output, and at the end prints them on a separate line of skipped tests so they can be distinguished. They are also distinguished in the `_result.json` file as a skipped test with reason "too large". Signed-off-by: Damien George <damien@micropython.org>	2025-06-05 15:15:31 +10:00
Damien George	4dff9cbf1a	tests/run-tests.py: Change _results.json to have a combined result list. ... The `_results.json` output of `run-tests.py` was recently changed in 7a55cb6b36 to add a list of passed and skipped tests. The way this was done turned out to be not general enough, because we want to add another type of result, namely tests that are skipped because they are too large. Instead of having separate lists in `_results.json` for each kind of result (pass, fail, skip, skip too large, etc), this commit changes the output form of `_results.json` so that it stores a single list of 3-tuples of all tests that were run: [(test_name, result, reason), ...] That's more general and allows adding a reason for skipped and failed tests. At the moment this reason is just an empty string, but can be improved in the future. Signed-off-by: Damien George <damien@micropython.org>	2025-06-03 10:07:29 +10:00
Damien George	7a55cb6b36	tests/run-tests.py: Add list of passed/skipped tests to _result.json. ... The output `_result.json` file generated by `run-tests.py` currently contains a list of failed tests. This commit adds to the output a list of passed and skipped tests, and so now provides full information about which tests were run and what their results were. Signed-off-by: Damien George <damien@micropython.org>	2025-05-18 00:31:48 +10:00
Yoctopuce dev	bdb7e036d2	extmod/asyncio: Fix early exit of asyncio scheduler. ... This commit fixes three open issues related to the asyncio scheduler exiting prematurely when the main task queue is empty, in cases where CPython would not exit (for example, because the main task is not done because it's on a different queue). In the first case, the scheduler exits because running a task via `run_until_complete` did not schedule any dependent tasks. In the other two cases, the scheduler exits because the tasks are queued in an event queue. Tests have been added which reproduce the original issues. These test cases document the unauthorized use of `Event.set()` from a soft IRQ, and are skipped in unsupported environments (webassembly and native emitter). Fixes issues #16759, #16569 and #16318. Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-05-07 14:56:47 +10:00
Damien George	fa42487e45	extmod/moddeflate: Keep DeflateIO state consistent on window alloc fail. ... Allocation of a large compression window may fail, and in that case keep the `DeflateIO` state consistent so its other methods (such as `close()`) still work. Consistency is kept by only updating the `self->write` member if the window allocation succeeds. Thanks to @jimmo for finding the bug. Signed-off-by: Damien George <damien@micropython.org>	2025-03-27 11:58:59 +11:00
Angus Gratton	b4cf82b2d6	test/run-tests: Print a note if it looks like unittest.main() missing. ... This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-03-04 10:45:23 +11:00
Angus Gratton	5f01232dd7	tests/run-tests: Remove any 'expected' file from a unittest run. ... This won't be generated normally, but a failed run (for example, from a unittest with an error or which doesn't call unittest.main()) will generate one. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-03-04 10:45:23 +11:00
Christian Clauss	8ce7a58be2	tests: Four typos in tests directory. ... Found by codespell. Signed-off-by: Christian Clauss <cclauss@me.com>	2025-02-25 23:34:53 +11:00
Damien George	372ecfef02	tests/run-tests.py: Give more information when CPython crashes. ... To make it easier to diagnose why CPython crashed. Signed-off-by: Damien George <damien@micropython.org>	2025-02-11 16:41:48 +11:00
Damien George	966eb00394	tests/run-tests.py: Implement getcwd on __FS hook filesystem. ... This method is needed by tests like `extmod/vfs_rom.py`. Signed-off-by: Damien George <damien@micropython.org>	2025-01-06 17:55:11 +11:00
Damien George	91e30df5f2	tests/run-tests.py: Set __main__ module to __injected_test. ... When using unittest (for example) with injected mpy files, not only does the name of the main test module need to be `__main__`, but also the `__main__` module should correspond to this injected module. Otherwise the unittest test won't be detected. Signed-off-by: Damien George <damien@micropython.org>	2025-01-06 17:48:22 +11:00
Alessandro Gatti	931a768f55	tests/run-tests.py: Detect inlineasm support and add tests if needed. ... This commit implements a method to detect at runtime if inline assembler support is enabled, and if so which platform it targets. This allows clean test runs even on modified version of ARM-based ports where inline assembler support is disabled, running inline assembler tests on ports that have such feature not enabled by default and manually enabled, and allows to always run the correct inlineasm tests for ports that support more than one architecture (esp32, qemu, rp2). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-01-02 11:52:28 +11:00
Alessandro Gatti	268acb714d	py/emitinlinerv32: Add inline assembler support for RV32. ... This commit adds support for writing inline assembler functions when targeting a RV32IMC processor. Given that this takes up a bit of rodata space due to its large instruction decoding table and its extensive error messages, it is enabled by default only on offline targets such as mpy-cross and the qemu port. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-01-02 11:49:10 +11:00
Alessandro Gatti	a5270c84cf	tests/inlineasm: Make room for RV32IMC inline asm tests. ... Thumb/Thumb2 tests are now into their own subdirectory, as RV32IMC-specific tests will be added as part of the RV32 inline assembler support. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-01-01 10:44:50 +01:00
Damien George	a3128f89cc	tests: Fix all file ioctl's to support only MP_STREAM_CLOSE. ... A return value of 0 from Python-level `ioctl()` means success, but if that's returned unconditionally it means that the method supports all ioctl calls, which is not true. Returning 0 without doing anything can potentially lead to a crash, eg for MP_STREAM_SEEK which requires returning a value in the passed-in struct pointer. This commit makes it so that all `ioctl()` methods respond only to MP_STREAM_CLOSE, ie they return -1 (indicating error) for all other ioctl calls. Signed-off-by: Damien George <damien@micropython.org>	2024-12-20 21:52:19 +11:00
Damien George	e323da7291	tests/run-tests.py: Set name of injected test module to '__main__'. ... Running unittest-based tests with --via-mpy is currently broken, because the unittest test needs the module to be named `__main__`, whereas it's actually called `__injected_test`. Fix this by changing the name when the file is opened. Signed-off-by: Damien George <damien@micropython.org>	2024-12-19 15:12:04 +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
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	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	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	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
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
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
Damien George	659113825d	qemu: Rename qemu-arm port to qemu. ... Because this port now supports multiple architectures. Signed-off-by: Damien George <damien@micropython.org>	2024-09-06 11:08:39 +10:00
Damien George	3ea1ce63da	all: Remove remaining qemu-riscv references. ... Signed-off-by: Damien George <damien@micropython.org>	2024-09-06 11:08:22 +10:00
Damien George	6be1dbc784	tests/run-tests.py: Automatically detect native arch and mpy-cross flag. ... Now that some ports support multiple architectures (eg esp32 has both Xtensa and RISC-V CPUs) it's no longer possible to set mpy-cross flags based on the target, eg `./run-tests.py --target esp32`. Instead this commit makes it so the `-march=xxx` argument to mpy-cross is detected automatically via evaluation of `sys.implementation._mpy`. Signed-off-by: Damien George <damien@micropython.org>	2024-09-04 16:34:01 +10:00
Damien George	d9a0fdda9a	qemu-arm: Rework to provide a REPL and run tests via a pty serial port. ... Currently, the qemu-arm (and qemu-riscv) port has two build modes: - a simple test that executes a Python string; and - a full test that uses tinytest to embed all tests within the firmware, then executes that and captures the output. This is very different to all the other ports. A difficulty with using tinytest is that with the large number of tests the firmware overflows its virtual flash size. It's also hard to run tests via .mpy files and with the native emitter. Being different to the other ports also means an extra burden on maintenance. This commit reworks the qemu-arm port so that it has a single build target that creates a standard firmware which has a REPL. When run under qemu-system-arm, the REPL acts like any other bare-metal port, complete with soft reset (use machine.reset() to turn it off and exit qemu-system-arm). This approach gives many benefits: - allows playing with a REPL without hardware; - allows running the test suite as it would on a bare-metal board, by making qemu-system-arm redirect the UART serial of the virtual device to a /dev/pts/xx file, and then running run-tests.py against that serial device; - skipping tests is now done via the logic in `run-tests.py` and no longer needs multiple places to define which tests to skip (`tools/tinytest-codegen.py`, `ports/qemu-arm/tests_profile.txt` and also `tests/run-tests.py`); - allows testing/using mpremote with the qemu-arm port. Eventually the qemu-riscv port would have a similar change. Prior to this commit the test results were: 743 tests ok. (121 skipped) With this commit the test results are: 753 tests performed (22673 individual testcases) 753 tests passed 138 tests skipped More tests are skipped because more are included in the run. But overall more tests pass. Signed-off-by: Damien George <damien@micropython.org>	2024-08-28 11:52:08 +10:00
Damien George	86aa61918a	tests/run-tests.py: Skip additional tests when slice unavailable. ... Both of these tests require slice to be enabled. Signed-off-by: Damien George <damien@micropython.org>	2024-08-28 11:23:11 +10:00
Angus Gratton	80616aee71	tests/run-tests.py: Enable stress tests on esp32 port. ... Now passing on ESP32-S3 and ESP32-C3. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2024-08-14 12:56:56 +10:00