Issue 315

This PR fixes #315. It turns out that (1) the invalid SetUpFixture was not getting a FailureSite.SetUp and (2) the children were not being recursively set to NotRunnable with the result that the console report was not showing any information about the failure.