| Bug #52220 | rpl_show_slave_running fails on some platforms | ||
|---|---|---|---|
| Submitted: | 19 Mar 2010 13:54 | Modified: | 26 Mar 2010 19:28 |
| Reporter: | Alexander Nozdrin | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | Tests: Replication | Severity: | S3 (Non-critical) |
| Version: | 6.0 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
| Tags: | experimental, pb2, test failure | ||
[20 Mar 2010 2:08]
MySQL Verification Team
Thank you for the bug report.
[miguel@tikal mysql-test]$ ./mtr rpl.rpl_show_slave_running
Logging: ./mtr rpl.rpl_show_slave_running
100319 23:06:07 [Note] Buffered information: Performance schema disabled (reason: start parameters).
100319 23:06:07 [Note] Plugin 'FEDERATED' is disabled.
MySQL Version 6.0.14
Checking supported features...
- skipping ndbcluster, mysqld not compiled with ndbcluster
- SSL connections supported
- binaries are debug compiled
Collecting tests...
- adding combinations for rpl
vardir: /home/miguel/bzr/6.0-codebase-bugfixing/mysql-test/var
Removing old var directory...
Creating var directory '/home/miguel/bzr/6.0-codebase-bugfixing/mysql-test/var'...
Installing system database...
Using server port 38263
==============================================================================
TEST RESULT TIME (ms)
------------------------------------------------------------
worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
rpl.rpl_show_slave_running 'row' [ fail ]
Test ended at 2010-03-19 23:06:31
[26 Mar 2010 19:28]
Andrei Elkin
Fixed with Bug#51648 patch.
Description: Tree: 6.0-codebase-bugfixing. Symptoms: --------------------------------------------------------------- rpl.rpl_show_slave_running [ fail ] Test ended at 2010-03-18 12:18:45 CURRENT_TEST: rpl.rpl_show_slave_running mysqltest: At line 14: query 'SELECT GET_LOCK($debug_lock, 1000)' failed: 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 1000)' at line 1 The result from queries just before the failure was: stop slave; drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9; reset master; reset slave; drop table if exists t1,t2,t3,t4,t5,t6,t7,t8,t9; start slave; include/stop_slave.inc --------------------------------------------------------------- Making the test case experimental due to this bug. How to repeat: Logs: - http://tinyurl.com/yan73dz - http://tinyurl.com/yk6lp8q Builds: - http://pb2.norway.sun.com/web.py?template=push_details&push=1086553