1
0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2024-12-29 04:50:03 +01:00
RIOT/tests/mutex_order
Marian Buschsieweke 06d560f408
tests: Added atmega328p to Makefile.ci
Added the atmega328p board to the BOARD_INSUFFICIENT_MEMORY list where needed.
2019-10-21 12:54:46 +02:00
..
tests tests: move testrunner import up 2018-08-13 14:11:24 +02:00
main.c tests: mutex_order: remove xtimer dependency 2016-11-03 16:37:24 +01:00
Makefile tests: BOARD_INSUFFICIENT_MEMORY -> Makefile.ci 2019-10-17 15:11:59 +02:00
Makefile.ci tests: Added atmega328p to Makefile.ci 2019-10-21 12:54:46 +02:00
README.md tests: mutex_order: fixed and updated README 2016-11-03 16:37:39 +01:00

Expected result

When successful, you should see 5 different threads printing their PID and priority. 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). The output should look like the following:

main(): This is RIOT! (Version: xxx)
Mutex order test
Please refer to the README.md for more information

T3 (prio 6): trying to lock mutex now
T4 (prio 4): trying to lock mutex now
T5 (prio 0): trying to lock mutex now
T6 (prio 2): trying to lock mutex now
T7 (prio 1): trying to lock mutex now
T5 (prio 0): unlocking mutex now
T7 (prio 1): unlocking mutex now
T6 (prio 2): unlocking mutex now
T4 (prio 4): unlocking mutex now
T3 (prio 6): unlocking mutex now

Test END, check the order of priorities above.

Background

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