MySQL Bugs: #23592: Running mysql-test-run.pl will cause warnings with assertion failures

Bug #23592	Running mysql-test-run.pl will cause warnings with assertion failures
Submitted:	24 Oct 2006 19:17	Modified:	7 Nov 2006 12:04
Reporter:	Jani Tolonen	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Tests	Severity:	S3 (Non-critical)
Version:	5.1 latest source from BK	OS:	Linux (Linux 64_x86)
Assigned to:		CPU Architecture:	Any

Description:
mysql-test-run will fail with assertion failures,
but no test case will actually fall (none say [fail]),
but the actual results will end up with warnings like
this:

Stopping All Servers
Shutting-down Instance Manager
All 516 tests were successful.
The servers were restarted 113 times
Spent 3738.726 seconds actually executing testcases
mysql-test-run: WARNING: Got errors/warnings while running tests, please examine "/home/build/mysql-5.1-lex-string/mysql-test/var/log/warnings" for details.
mysql-test-run: *** ERROR: there where failing test cases

In the warnings file I caught these:

error: Assertion .* failed, mysqld: log.cc:3373: int THD::binlog_write_table_map
(TABLE*, bool): Assertion `current_stmt_binlog_row_based && mysql_bin_log.is_ope
n()' failed.
, mysqld: log.cc:3373: int THD::binlog_write_table_map(TABLE*, bool): Assertion
`current_stmt_binlog_row_based && mysql_bin_log.is_open()' failed.

So this seems to be related to replication.

I had to tweak the lib/mtr_report.pl before I got the warnings in to the
warnings file. It seems that adding double quotes around this line:

print WARN $_;

-> 

print WARN "$_";

Not sure why it got here without printing to the file without.

How to repeat:
cd mysql-test
./mysql-test-run.pl --force --mysqld=--binlog-format=mixed

Please note that I did not get the warnings without the last option.
That is also default when one runs "make test-force".

Thank you for a problem report. Please, specify exact Changeset used. I've got test failures:

mysql-test-run in default mode: *** Failing the test(s): bug20951 bug21881 rpl00
0018 rpl_chain_temp_table rpl_failsafe

(note several rpl_* ones) with

ChangeSet@1.2320, 2006-10-20 11:15:54+02:00

on my Suse 9.3 (x86).

Here are the three latest changesets.

Valeriy: It looks like your tree is even more broken, so that should be fixed first. I doubt that this is fixed, instead just got masked by extra problems.

ChangeSet@1.2312, 2006-10-16 15:40:40-04:00, mikael@dator5.(none) +11 -0
  Merge dator5.(none):/home/pappa/clean-mysql-5.1
  into  dator5.(none):/home/pappa/bug18198
  MERGE: 1.2273.68.18

ChangeSet@1.2255.83.1, 2006-10-16 19:57:33+03:00, jani@ua141d10.elisa.omakaista.fi +22 -0
  Changed several char* to LEX_STRING*.

ChangeSet@1.2311, 2006-10-13 14:42:50+04:00, kroki@moonlight.intranet +3 -0
  Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-real
  into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.1-real
  MERGE: 1.1810.2078.32

ChangeSet@1.1810.2078.32, 2006-10-13 14:40:26+04:00, kroki@moonlight.intranet +3 -0
  Merge moonlight.intranet:/home/tomash/src/mysql_ab/mysql-4.1-bug9678
  into  moonlight.intranet:/home/tomash/src/mysql_ab/mysql-5.0-real
  MERGE: 1.1616.2782.1

Seems to be a duplicate of BUG#23110.

Duplicate of bug #23110. At least, should be tested again after that bug will be fixed.