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 |
||
|---|---|---|
| .. | ||
| gear | ||
| mem | ||
| DIR_INFO | ||
| test-filedescriptors.c | ||
| test-filehandles.c | ||
| test-fileheader.c | ||
| test-filemmap.c | ||
| test-resourcecollector.c | ||
| test-threadpool.c | ||
| test-threads.c | ||