History

Marian Buschsieweke eb1279005c

tests: Cleanup access to internal variables

Replace direct accesses to sched_active_thread and sched_active_pid with
the helper functions thread_getpid() and thread_get_active(). This serves
two purposes:

1. It makes accidental writes to those variable from outside core less likely.
2. Casting off the volatile qualifier is now well contained to those two
   functions

2020-08-24 09:08:01 +02:00

tests

tests: move testrunner import up

2018-08-13 14:11:24 +02:00

main.c

tests: Cleanup access to internal variables

2020-08-24 09:08:01 +02:00

Makefile

tests: remove uneeded DISABLE_MODULE+=auto_init

2020-02-12 16:51:34 +01:00

Makefile.ci

examples,tests: Updated Makefile.ci

2020-07-27 20:51:52 +02:00

README.md

thread_msg_block_wo_queue: add README & pexpect script, extend comments

2017-03-07 09:06:42 -08:00

README.md

Background

Tests for the same situation as thread_msg_block_w_queue, but without an initialized message queue for the main thread:

This test application checks for the behavior reported in https://github.com/RIOT-OS/RIOT/issues/100:

Usually, when a thread (here sender_thread) sends a message to another thread (here the main thread) whose message queue already holds a message, the message of sender_thread is copied into main's message queue and sender_thread is set to STATUS_PENDING. However, this should not happen if sender_thread is currently in STATUS_REPLY_BLOCKED mode, since it is in the middle of a different, blocking send.

In the aforementioned issue, it was reported that this undesired behavior was happening. It has been fixed since, and this test ensures that it doesn't re-occur again.

Expected result

The output should look as follows:

sender_thread start
main thread alive

If you see

ERROR: sender_thread should be blocking

something went wrong.