Bug #15727 xid in bin log comment field cause tests to fail
Submitted: 14 Dec 2005 1:39 Modified: 14 Dec 2005 21:17
Reporter: Jonathan Miller Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.1 OS:Linux (Linux)
Assigned to: Guilhem Bichot CPU Architecture:Any

[14 Dec 2005 1:39] Jonathan Miller
The xid in the bin log comment fail can cause tests to fail.

If the tests are run in a row you will get one value to xid, but if a test is done as a single test, you will get another value for xid.

Example of this is binlog_stm_mix_innodb_myisam.test

How to repeat:
Run test as --do-test=bin and then run test as --do-test=binlog_stm_mix_innodb_myisam

xid will have different results causing one of the tests to fail.

Suggested fix:
remove xid from bin log comment field.
[14 Dec 2005 21:17] Guilhem Bichot
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

fixed by adding option --binlog-show-xid=0|1 in debug builds, limiting the two relevant test files
to be skipped on non-debug builds, and inserting --binlog-show-xid=0 in mysql-test-run.*.
A finer solution will be to implement a --replace-regex command in mysqltest, later.
Nothing to document as this is an option in debug builds only, with this description:
   "Option used by mysql-test for debugging and testing: "
   "do not display the XID in SHOW BINLOG EVENTS; "
   "may be removed in future versions",
(we already have such for-debug options: abort-slave-event-count etc).