Bug #39314 | falcon_bug_26433 fails with an offset of 1 in row numbers in expected warnings | ||
---|---|---|---|
Submitted: | 8 Sep 2008 14:48 | Modified: | 19 Mar 2009 13:11 |
Reporter: | John Embretsen | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S3 (Non-critical) |
Version: | 6.0.7 | OS: | Any |
Assigned to: | Hakan Küçükyılmaz | CPU Architecture: | Any |
Tags: | F_TEST, test failure |
[8 Sep 2008 14:48]
John Embretsen
[16 Dec 2008 17:58]
Hakan Küçükyılmaz
Running the test with InnoDB as storage engine shows same offset "error". I am adjusting the test and moving it back home to falcon test suite.
[16 Dec 2008 21:21]
Bugs System
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/61825 2939 Hakan Kuecuekyilmaz 2008-12-16 Fix for Bug #39314 falcon_bug_26433 fails with an offset of 1 in row numbers in expected warnings
[18 Dec 2008 21:52]
Hakan Küçükyılmaz
I adjusted the result file after testing this test case with InnoDB, which shows the same change in the warnings. This test was originally written to crash Falcon using different seed values for rand(). However, different seed values produce a different set of warnings.
[13 Feb 2009 7:25]
Bugs System
Pushed into 6.0.10-alpha (revid:alik@sun.com-20090211182317-uagkyj01fk30p1f8) (version source revid:hky@sun.com-20081216212048-0kf03zshuob7wwsa) (merge vers: 6.0.9-alpha) (pib:6)
[19 Mar 2009 13:11]
John Embretsen
Looks like a fix for this was merged into main about a month ago, but the bug system has not caught up with it. Setting status to Closed (there is nothing to document, as this was a test case issue).