> I'm not that familiar with the test harness, but would it be possible to
> get test_multiprocessing to log an error when it has to be skipped.

Well, there should be a skip message next to the test_multiprocessing line 
in the results.  I'm not sure whether that's the sort of thing you mean.

Unfortunately it looks like both runs (6.4 and 7.2) were prematurely 
terminated by test_curses before they even got as far as 
test_multiprocessing.  I might try running them again and hope for a 
different random test ordering.

I'm also seeing warnings about HAVE_BROKEN_POSIX_SEMAPHORES being 
redefined, in Python/thread_pthread.h;  I'll take another look at this 
next week (no access to the FreeBSD machine at the moment).