FamilyMember::allocateNextMember() was actually a post-increment, so (different than with TypedCounter) here no correction is necessary As an asside, WorkForce_test is sometimes unstable immediately after a build. Seemingly a headstart of 50µs is not enough to compensate for scheduler leeway |
||
|---|---|---|
| .. | ||
| activity-detector-test.cpp | ||
| activity-detector.hpp | ||
| block-flow-test.cpp | ||
| scheduler-activity-test.cpp | ||
| scheduler-commutator-test.cpp | ||
| scheduler-invocation-test.cpp | ||
| scheduler-usage-test.cpp | ||
| work-force-test.cpp | ||