Bug #47617 | mtr doesn't handle well suppressions on windows | ||
---|---|---|---|
Submitted: | 24 Sep 2009 14:46 | Modified: | 1 Oct 2009 10:27 |
Reporter: | Georgi Kodinov | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | Tools: MTR / mysql-test-run | Severity: | S7 (Test Cases) |
Version: | OS: | Any (Windows and Linux and Solaris) | |
Assigned to: | Bjørn Munch | CPU Architecture: | Any |
[24 Sep 2009 14:46]
Georgi Kodinov
[24 Sep 2009 14:51]
Georgi Kodinov
Looks like mtr2 is not handling suppressions in mysql-test/include/mtr_warnings.sql as well. I have : rpl.rpl_timezone [ fail ] Found warnings/errors in server log file! Test ended at 2009-09-23 22:24:13 file_name line G:/pb2/test/sb_1-763829-1253735280.22/mysql-5.1.40-win-x86_64-test/mysql-test/var-n_mix/log/mysqld.2.err 090924 4:24:13 [Warning] Slave: Unknown table 't1' Error_code: 1051 ^ Found warnings!! ok mysqltest: Logging to ''. Despite the fact that there's the following suppression in the file : 157 /* 158 rpl_extrColmaster_*.test, the slave thread produces warnings 159 when it get updates to a table that has more columns on the 160 master 161 */ 162 ("Slave: Unknown column 'c7' in 't15' Error_code: 1054"), 163 ("Slave: Can't DROP 'c7'.* 1091"), 164 ("Slave: Key column 'c6'.* 1072"), 165 ("Slave I/O: The slave I/O thread stops because a fatal error is encountered when it try to get the value of SERVER_ID variable from master."), 166 (".SELECT UNIX_TIMESTAMP... failed on master, do not trust column Seconds_Behind_Master of SHOW SLAVE STATUS"),
[24 Sep 2009 14:54]
Georgi Kodinov
doesn't seem to be windows specific : same problems on some pb2 linux and solaris hosts.
[30 Sep 2009 7:17]
Bjørn Munch
I suspect this is a duplicate of Bug #46996
[1 Oct 2009 10:27]
Bjørn Munch
Duplicate of Bug #46996.