← Back to team overview

linux-traipu team mailing list archive

[Bug 798968] [NEW] dbqp's crashme mode does not exit gracefully if crashme cannot run

 

Public bug reported:

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.

** Affects: drizzle
     Importance: Medium
     Assignee: Patrick Crews (patrick-crews)
         Status: Fix Committed

** Affects: drizzle/fremont
     Importance: Medium
     Assignee: Patrick Crews (patrick-crews)
         Status: Fix Committed

** Branch linked: lp:~patrick-crews/drizzle/bug798968_crashme

** Changed in: drizzle
       Status: New => Fix Committed

** Changed in: drizzle
   Importance: Undecided => Medium

** Changed in: drizzle
     Assignee: (unassigned) => Patrick Crews (patrick-crews)

** Also affects: drizzle/fremont
   Importance: Medium
     Assignee: Patrick Crews (patrick-crews)
       Status: Fix Committed

** Changed in: drizzle/fremont
    Milestone: None => 2011-06-20

-- 
You received this bug notification because you are a member of UBUNTU -
AL, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/798968

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

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Fix Committed
Status in Drizzle fremont series:
  Fix Committed

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/798968/+subscriptions


Follow ups

References