linux-traipu team mailing list archive

[Patrick Crews <794547@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When running the crash-me test as we do in drizzle-automation, we are seeing the following two failures:
It should be noted that our crash-me jenkins slave has been down for a while and this may have slipped through the cracks.
Need to maybe do bzrfind to pinpoint the regression.

To repeat, from the linked branch, run:
./dbqp --mode=crashme  

sql-bench is located in-tree, all you will need is the dbd:drizzle driver installed.
20110607-225755  ===============================================================
20110607-225755  TEST NAME                                  [ RESULT ] TIME (ms)
20110607-225755  ===============================================================
20110607-225755  main.crashme                               [ fail ]   153271
20110607-225755  func_extra_to_days=error		# Function TO_DAYS
20110607-225755  ###
20110607-225755  ###<select to_days('1996-01-01') from crash_me_d
20110607-225755  ###>2450084
20110607-225755  ###We expected '729024' but got '2450084'
20110607-225755  func_odbc_timestampadd=error		# Function TIMESTAMPADD
20110607-225755  ###
20110607-225755  ###<select timestampadd(SQL_TSI_SECOND,1,'1997-01-01 00:00:00')
20110607-225755  ###>1997-01-01 00:00:01.000000
20110607-225755  ###We expected '1997-01-01 00:00:01' but got '1997-01-01 00:00:01.000000'
20110607-225755  ###
20110607-225755  ###<select {fn timestampadd(SQL_TSI_SECOND,1,{ts '1997-01-01 00:00:00'}) }
20110607-225755  ###>1997-01-01 00:00:01.000000
20110607-225755  ###We expected '1997-01-01 00:00:01' but got '1997-01-01 00:00:01.000000'
20110607-225755  
20110607-225755 ERROR Failed test.  Use --force to execute beyond the first test failure

** Affects: drizzle
     Importance: High
         Status: Confirmed

** Changed in: drizzle
       Status: New => Confirmed

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

** Branch linked: lp:~patrick-crews/drizzle/drizzle-sqlbench-crashme

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

Title:
  drizzle failing sql-bench crash-me test

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Confirmed

Bug description:
  When running the crash-me test as we do in drizzle-automation, we are seeing the following two failures:
  It should be noted that our crash-me jenkins slave has been down for a while and this may have slipped through the cracks.
  Need to maybe do bzrfind to pinpoint the regression.

  To repeat, from the linked branch, run:
  ./dbqp --mode=crashme  

  sql-bench is located in-tree, all you will need is the dbd:drizzle driver installed.
  20110607-225755  ===============================================================
  20110607-225755  TEST NAME                                  [ RESULT ] TIME (ms)
  20110607-225755  ===============================================================
  20110607-225755  main.crashme                               [ fail ]   153271
  20110607-225755  func_extra_to_days=error		# Function TO_DAYS
  20110607-225755  ###
  20110607-225755  ###<select to_days('1996-01-01') from crash_me_d
  20110607-225755  ###>2450084
  20110607-225755  ###We expected '729024' but got '2450084'
  20110607-225755  func_odbc_timestampadd=error		# Function TIMESTAMPADD
  20110607-225755  ###
  20110607-225755  ###<select timestampadd(SQL_TSI_SECOND,1,'1997-01-01 00:00:00')
  20110607-225755  ###>1997-01-01 00:00:01.000000
  20110607-225755  ###We expected '1997-01-01 00:00:01' but got '1997-01-01 00:00:01.000000'
  20110607-225755  ###
  20110607-225755  ###<select {fn timestampadd(SQL_TSI_SECOND,1,{ts '1997-01-01 00:00:00'}) }
  20110607-225755  ###>1997-01-01 00:00:01.000000
  20110607-225755  ###We expected '1997-01-01 00:00:01' but got '1997-01-01 00:00:01.000000'
  20110607-225755  
  20110607-225755 ERROR Failed test.  Use --force to execute beyond the first test failure