1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
RIOT/tests/rmutex
Marian Buschsieweke e197abb6a3
tests/rmutex: Drop output dump from README.md
Fixes https://github.com/RIOT-OS/RIOT/issues/19140
Fixes https://github.com/RIOT-OS/RIOT/issues/19298

We use test scripts to automatically classify the output of a test
application as passing / failing. Users are not expected to manually
compare the output with a dump of the output in a readme.
2023-03-15 12:58:09 +01:00
..
tests tests/rmutex: refactor the test to avoid having to know the thread IDs 2020-06-09 23:05:30 +02:00
main.c tests/rmutex: clean up test and reduce stack size 2023-02-22 09:39:01 +01:00
Makefile tests: BOARD_INSUFFICIENT_MEMORY -> Makefile.ci 2019-10-17 15:11:59 +02:00
Makefile.ci tests/rmutex: clean up test and reduce stack size 2023-02-22 09:39:01 +01:00
README.md tests/rmutex: Drop output dump from README.md 2023-03-15 12:58:09 +01:00

Expected result

When successful, you should see 5 different threads printing their PID, priority and recursion depth. The thread with the lowest priority should be able to lock (and unlock) the mutex first, followed by the other threads in the order of their priority (highest next). If two threads have the same priority the thread who comes first in the run queue (in this test this is the one with the lower thread id) should acquire the lock.

Background

This test application stresses a mutex with a number of threads waiting on it.