-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sys/test_utils/dummy_thread: initial commit #14227
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack, please squash.
Are you sure we should skip the compile test?
it is not used anywhere... |
I'm a bit hesistant with merging what is effectively dead code, but I don't really see the need to add a separate test for this. Does it make sense to add this as a default module to one of the tests, maybe just the unittests? |
OK, it'll increase RAM usage like if adding another idle thread, let's see if that's ok. |
I added it to tests/test_utils, seems most fitting. |
This commit adds a module that just creates a thread that does nothing, at boot time, in auto_init().
Contribution description
While looking at # #14181, I needed a quick way to add a thread. So this dummy thread module was born. If used, the module will start a dummy thread that only sleeps, in auto_init().
Use like this, to trick tests that assume a constant number of threads:
USEMODULE+=dummy_thread make -Ctests/rmutex flash test
.This module is not used otherwise.
Testing procedure
Issues/PRs references