MySQL Bugs: #17360: sp-code test case broken

Bug #17360	sp-code test case broken
Submitted:	14 Feb 2006 3:02	Modified:	15 Feb 2006 13:14
Reporter:	Jim Winstead	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Stored Routines	Severity:	S1 (Critical)
Version:	5.1-bk	OS:	Linux (Linux, x86_64)
Assigned to:	Magnus Blåudd	CPU Architecture:	Any

Description:
The sp-code test case fails using the latest BK source.

How to repeat:
-------------------------------------------------------
*** r/sp-code.result    2006-02-09 23:59:36.000000000 +0300
--- r/sp-code.reject    2006-02-14 06:01:46.000000000 +0300
***************
*** 155,165 ****
  0     stmt 9 "drop temporary table if exists sudoku..."
  1     stmt 1 "create temporary table sudoku_work ( ..."
  2     stmt 1 "create temporary table sudoku_schedul..."
! 3     stmt 94 "call sudoku_init("
  4     jump_if_not 7(8) p_naive@0
  5     stmt 4 "update sudoku_work set cnt = 0 where ..."
  6     jump 8
! 7     stmt 94 "call sudoku_count("
  8     stmt 6 "insert into sudoku_schedule (row,col)..."
  9     set v_scounter@2 0
  10    set v_i@3 1
--- 155,165 ----
  0     stmt 9 "drop temporary table if exists sudoku..."
  1     stmt 1 "create temporary table sudoku_work ( ..."
  2     stmt 1 "create temporary table sudoku_schedul..."
! 3     stmt 95 "call sudoku_init("
  4     jump_if_not 7(8) p_naive@0
  5     stmt 4 "update sudoku_work set cnt = 0 where ..."
  6     jump 8
! 7     stmt 95 "call sudoku_count("
  8     stmt 6 "insert into sudoku_schedule (row,col)..."
  9     set v_scounter@2 0
  10    set v_i@3 1

Who updated it? How did they push without fixing the test case? Why haven't they fixed it yet?

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/2651

Pushed to 5.1