Comment 9 for bug 1499229

It seems the test in question may not be the problem. Disabling that test with a memcheck filter results in the same number of valgrind failures at the end of mir_unit_tests. So they're happening sooner.

Now I look back through them, it seems like most of the issues were what Cemil just fixed and landed. So wait and see how that fix helps...

The confusion about this bug seems to stem from the errors occurring before ThreadedDispatcherSignalTest.keeps_dispatching_after_signal_interruption starts, forks and returns. So the child process is always seen as failing despite the fact the errors didn't occur in that test at all, but occurred before it started. So I'm assuming forked processes inherit the valgrind error list from their parents.