dbqp's crashme mode does not exit gracefully if crashme cannot run
Bug #798968 reported by
Patrick Crews
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_
<type 'exceptions.
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
lp://staging/~patrick-crews/drizzle/bug798968_crashme
- Drizzle Merge Team: Pending requested
-
Diff: 52 lines (+23/-22)1 file modifiedtests/lib/sqlbench/sqlbench_test_execution.py (+23/-22)
Changed in drizzle: | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
assignee: | nobody → Patrick Crews (patrick-crews) |
To post a comment you must log in.