kaspar/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2025-12-16 10:03:50 +01:00
Code Releases Activity

tests: mutex_order: fixed and updated README

Browse Source
This commit is contained in:
Oleg Hahm 2016-11-03 16:37:39 +01:00
parent e0ede745a6
commit a5245769d3
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
tests/mutex_order/README.md
View File

@ -1,25 +1,25 @@
Expected result
===============
When successful, you should see 10 different threads printing their PID and
priority. The thread with the lowest priority will print its status first,
followed by the other threads in the order of their priority (highest next). The
output should look like the following:
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): locking mutex now
T4 (prio 0): locking mutex now
T5 (prio 4): locking mutex now
T6 (prio 2): locking mutex now
T7 (prio 1): locking mutex now
T3 (prio 6): unlocking mutex now
T4 (prio 0): unlocking mutex now
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
T5 (prio 4): unlocking mutex now
T4 (prio 4): unlocking mutex now
T3 (prio 6): unlocking mutex now
Test END, check the order of priorities above.
```