dbqp's crashme mode does not exit gracefully if crashme cannot run

Bug #798968 reported by Patrick Crews
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Medium
Patrick Crews
7.1
Fix Released
Medium
Patrick Crews

Bug Description

In the event crashme doesn't run (say we are missing dbd::drizzle on the machine), It is currently dying in an annoying fashion:
20110617-202601 INFO Executing crash-me: $DRIZZLE_TEST_DIR/sql-bench/crash-me --server=drizzled --force --dir=$DRIZZLE_TEST_WORKDIR --connect-options=port=$MASTER_MYPORT --verbose --debug --user=root --config-file=/home/hudson/hudson/workspace/drizzle-param-crashme-exp/tests/workdir/drizzle.cfg
<type 'exceptions.Exception'> list index out of range
20110617-202602 INFO Stopping all running servers...
Notifying upstream projects of job completion
Finished: SUCCESS

This should be considered Fail of the highest order...working on a patch to fix this.

Related branches

Changed in drizzle:
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → Patrick Crews (patrick-crews)
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.