| Bug #14291 | Various rpl test fail in 5.1 | ||
|---|---|---|---|
| Submitted: | 25 Oct 2005 13:25 | Modified: | 28 Oct 2005 16:13 |
| Reporter: | Jonas Oreland | Email Updates: | |
| Status: | Closed | ||
| Category: | Server | Severity: | S3 (Non-critical) |
| Version: | 5.1 | OS: | Linux (Linux) |
| Assigned to: | Antony Curtis | Target Version: | |
[25 Oct 2005 16:13]
Miguel Solorzano
TEST RESULT ------------------------------------------------------- rpl_auto_increment [ fail ] Errors are (from /home/miguel/dbs/mysql-5.1/mysql-test/var/log/mysqltest-time) :
[25 Oct 2005 16:13]
Miguel Solorzano
TEST RESULT ------------------------------------------------------- rpl_auto_increment [ fail ] Errors are (from /home/miguel/dbs/mysql-5.1/mysql-test/var/log/mysqltest-time) :
[28 Oct 2005 16:13]
Antony Curtis
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
http://www.mysql.com/doc/en/Installing_source_tree.html
Description: rpl_auto_increment rpl_commit_after_flush rpl_ddl rpl_failed_optimize rpl_innodb could not sync with master ('select master_pos_wait('master-bin.000001', 370)' returned NULL) I suspect that this has something to do with loadable storage engine push and handling of default storage engine. i.e mysqld --skip-innodb create table t1 (a int) engine = innodb; will fail, but used to work creating a table in myisam instead... But it's only a guess How to repeat: ./mysql-test-run --do-test=rpl_auto_increment Suggested fix: