summaryrefslogtreecommitdiff
path: root/taskflow/tests/unit/test_utils_threading_utils.py
Commit message (Collapse)AuthorAgeFilesLines
* Remove 2.6 classifier + 2.6 compatibility codeJoshua Harlow2015-06-211-8/+4
| | | | | | | | Fixes bug 1445827 Depends-On: I02e3c9aacef0b295a2f823a5cbaf11768a90cb82 Change-Id: I1db681803598ac1bc917fd74a99458bc61edf3f1
* Ensure the thread bundle stops in last to first orderJoshua Harlow2015-03-041-0/+46
| | | | | | | | | | Instead of stopping in first started to last started which is typically not desired (this is the starting order) we should do the reverse and stop in last to first instead (which is typically the expected stopping order) by default. Change-Id: Ic579438bc549d380c62c4d56c55c168de425adeb
* Add a thread bundle helper utility + testsJoshua Harlow2015-01-241-0/+115
To make it easier to create a bunch of threads in a single call (and stop them in a single call) create a concept of a thread bundle (similar to a thread group) that will call into a provided set of factories to get a thread, activate callbacks to notify others that a thread is about to start or stop and then perform the start or stop of the bound threads in a orderly manner. Change-Id: I7d233cccb230b716af41243ad27220b988eec14c