dbqp showing test failure, but not producing further output

[Patrick Crews]

We are seeing this on some test runs:
02 Mar 2011 20:52:40 : main.func_if [ pass ] 103
02 Mar 2011 20:52:40 : main.func_in [ fail ] 754
02 Mar 2011 20:52:41 : main.func_in_null_scan [ pass ] 422

[Patrick Crews (patrick-crews)]

Need to determine what is up - test failures normally report a diff between expected and actual results and the user should be provided with a warning if the test is failing due to bad server start (and there shouldn't have been any server start for this test)

[Patrick Crews (patrick-crews)]

This only seems to occur on some platforms, like Ubuntu Lucid. Still need to investigate further, but it would appear that drizzletest is signaling a failure but not producing output. Need to investigate other code paths that would cause this.

Not tied to server start - that is working correctly and would produce more output.