MySQL Bugs: #24529: Test 'synchronization' fails on Mac pushbuild

Bug #24529	Test 'synchronization' fails on Mac pushbuild
Submitted:	23 Nov 2006 0:55	Modified:	2 Jun 2007 10:21
Reporter:	Chuck Bell	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Tests	Severity:	S3 (Non-critical)
Version:	5.1.14	OS:	MacOS (Mac OS)
Assigned to:	Damien Katz	CPU Architecture:	Any
Tags:	sr5_1

Description:
The test 'synchronization' fails when run on the Mac platform. The test fails with the following error reported:

synchronization                [ fail ]

Errors are (from /Users/henry/pb/mysql-5.1/1369/mysql-5.1.14-beta-pb1369/mysql-test/var-ps_stm-6/log/mysqltest-time) :
mysqltest: At line 37: query 'CREATE TABLE t2 LIKE t1' failed: 1049: Unknown database 'test'

The pushbuild references for this bug are:
Build:
https://intranet.mysql.com/~knielsen/pb/getlog.pl?dir=mysql-5.1&entry=mkindahl@romeo.none-...

Test run:
https://intranet.mysql.com/~knielsen/pb/getlog.pl?dir=mysql-5.1&entry=mkindahl@romeo.none-...

There is a closed bug #7735 which is similar in some ways. It may provide additional information.

How to repeat:
Build the server on Mac OS/X with the following commands:
./configure --prefix=/usr/local/mysql --localstatedir=/usr/local/mysql/data --libexecdir=/usr/local/mysql/bin "--with-comment=MySQL Pushbuild Edition, build 1369" --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-zlib-dir=bundled --with-big-tables --with-readline --with-archive-storage-engine --with-big-tables --with-innodb --with-berkeley-db --with-example-storage-engine --with-blackhole-storage-engine --with-ndbcluster --with-federated-storage-engine --with-csv-storage-engine --with-ssl

make -j4

Run the test suite with the following command:
perl ./mysql-test-run.pl --tmpdir=/tmp/pbtmp-ps_stm-6 --vardir=var-ps_stm-6 --timer --force --ps-protocol --mysqld=--binlog-format=statement

 

Suggested fix:
The bug seems to be associated with losing connection to the test database. I have examined a number of the tests prior to synchronization and some seem to use test.t1 whereas others rely on the test suite performing the "uses test" command. I don't think this is the issue, but for consistency we may want to always specify the database in the test commands (e.g., "test.t1").

Also, it appears a number of tests execute "drop database test" commands. Most of these tests are run prior to the synchronization test. These tests are:

events_stress.test
grant.test
information_schema_db.test
ndb_blob.test
ndb_autodiscover.test
ndb_grant.test
removedb.test
rpl_auto_increment_11932.test
rpl_row_basic_11bugs.test

Interestingly, the test passes on both Windows and SUSE.

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/15894

ChangeSet@1.2371, 2006-11-27 23:19:53+02:00, monty@mysql.com +6 -0
  Disabled syncronization test at it fails on multiple platforms. (Bug #24529)
  Fixed that test_thr_alarm works

I cannot reprodue this on my OS X 10.4.9 intel machine. The bug is a bit old, I suggest turning the test back on and see if it still fails.

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/26634

ChangeSet@1.2506, 2007-05-14 15:21:36-04:00, dkatz@damien-katzs-computer.local +1 -0
  Bug #24529  	Test 'synchronization' fails on Mac pushbuild

Pushed into 5.1-main