| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-01-25 | allow reading fdt in tests | Kimplul | |
| 2025-04-22 | simplify generator scripts | Kimplul | |
| 2024-11-02 | initial exec support | Kimplul | |
| 2024-11-01 | test all ipc variants more-or-less properly | Kimplul | |
| 2024-11-01 | rpc actually marks and unmarks stack regions | Kimplul | |
| + Processes won't be able to read previous stack frames etc | |||
| 2024-08-30 | specify mabi and march | Kimplul | |
| 2024-08-26 | simplify tests | Kimplul | |
| 2024-08-21 | add malloc test | Kimplul | |
| 2024-08-18 | small fixes to issues reported by analyzer | Kimplul | |
| + Currently analyzer has to be run manually with something like make CFLAGS='-fanalyzer -Wno-analyzer-infinite-loop' I use an infinite loop as an assert, I know it's not great/technically UB but it's just a fallback. + Analyzer is still somewhat limited, I could add in more attributes about different functions, such as memory allocation sizes etc. + If I ever set up a CI pipeline, remember to use analyzer? | |||
| 2024-07-17 | make tests a bit more sensible | Kimplul | |
| + At least by my standards. Some amount of scripting going on, but should still be fine. Effectively, source.mk contains information to build the test, check.mk checks the generated log from running the test. As a results, check.mk should output OK into reports/$TEST/OK if everything went well, and anything else otherwise. The user can then look at reports/$TEST/log to see what went wrong. I expect to add some more features, such as starting QEMU with gdb and running a single test a bit easier than right now (same limitation as in the top level makefile, i.e. you have to specify make -f scripts/makefile $TEST from within `tests` and you must have ran `make check` at that point so that `tests.mk` is fully generated. Not huge issues, but slightly annoying, somewhat unsure how to work around them properly but we'll see. | |||
