dbqp showing test failure, but not producing further output

Bug #728077 reported by Patrick Crews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Confirmed
Wishlist
Patrick Crews

Bug Description

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

Revision history for this message
Patrick Crews (patrick-crews) wrote :

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)

Changed in drizzle:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Patrick Crews (patrick-crews)
Revision history for this message
Patrick Crews (patrick-crews) wrote :

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.

Changed in drizzle:
importance: High → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.