Bug #39314 falcon_bug_26433 fails with an offset of 1 in row numbers in expected warnings
Submitted: 8 Sep 2008 16:48 Modified: 19 Mar 14:11
Reporter: John H. Embretsen
Status: Closed
Category:Server: Falcon Severity:S3 (Non-critical)
Version:6.0.7 OS:Any
Assigned to: Bugs System Target Version:6.0
Tags: F_TEST, test failure
Triage: Triaged: D3 (Medium)

[8 Sep 2008 16:48] John H. Embretsen
Description:
The test falcon_bug_26433 is in the falcon_team suite and is currently failing with a
diff that was not seen back when the test was moved from the "falcon" suite to
"falcon_team":

TEST                           RESULT         TIME (ms)
-------------------------------------------------------

falcon_team.falcon_bug_26433   [ fail ]

--- mysql-test/suite/falcon_team/r/falcon_bug_26433.result     2008-08-15
09:39:22.000000000 +0300
+++ mysql-test/suite/falcon_team/r/falcon_bug_26433.reject     2008-09-08
17:28:14.000000000 +0300
@@ -77,7 +77,6 @@
 d
 d
 Warnings:
-Warning        1265    Data truncated for column 'b' at row 20
 Warning        1265    Data truncated for column 'b' at row 21
 Warning        1265    Data truncated for column 'b' at row 22
 Warning        1265    Data truncated for column 'b' at row 23
@@ -97,6 +96,7 @@
 Warning        1265    Data truncated for column 'b' at row 37
 Warning        1265    Data truncated for column 'b' at row 38
 Warning        1265    Data truncated for column 'b' at row 39
+Warning        1265    Data truncated for column 'b' at row 40
 Warning        1366    Incorrect string value: '\x92\x92\x92\x92\x92\x92...' for column
'c' at row 1
 Warning        1366    Incorrect string value: '\x92\x92\x92\x92\x92\x92...' for column
'c' at row 2
 Warning        1366    Incorrect string value: '\x92\x92\x92\x92\x92\x92...' for column
'c' at row 3

mysqltest: Result content mismatch

Tested on Red Hat Linux and Solaris 10 x86, using an up-to-date mysql-6.0-falcon-team
branch, 2008-09-08.

It seems that the row numbers in these expected warnings are offset by 1, for some
reason. The cause may be harmless and may only require an update of the test's result
file, but this needs to be properly investigated.

There is another bug, Bug #32697 - "falcon_bug_26433.test fails randomly", which shows
that this test case has been problematic before, but none of the reported failures are
similar to this one.

How to repeat:
perl ./mysql-test-run.pl --suite=falcon_team falcon_bug_26433
[16 Dec 2008 18:58] Hakan Kuecuekyilmaz
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 22: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 22:52] Hakan Kuecuekyilmaz
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 8: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 14:11] John H. 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).