| Bug #46824 | binlog_multi_engine test fails on PB-2 | ||
|---|---|---|---|
| Submitted: | 20 Aug 2009 10:02 | Modified: | 3 Oct 2009 12:57 |
| Reporter: | Andrei Elkin | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | Tests | Severity: | S3 (Non-critical) |
| Version: | 5.1 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | test failure | ||
[20 Aug 2009 10:02]
Andrei Elkin
[31 Aug 2009 11:04]
Andrei Elkin
binlog.binlog_multi_engine [ fail ]
Test ended at 2009-08-31 09:46:35
The test continues to fail and on some platforms PB2 logs some substantial
details, like in
http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2297
CURRENT_TEST: binlog.binlog_multi_engine
Start of 'mysql_cluster.1' cluster failed
- saving '/export/tmp/pb2/test/sb_1-720013-1251700961.96/mysql-5.1.36-hpux11.31-ia64-test/mysql-test/var/log/binlog.binlog_multi_engine/' to '/export/tmp/pb2/test/sb_1-720013-1251700961.96/mysql-5.1.36-hpux11.31-ia64-test/mysql-test/var/log/binlog.binlog_multi_engine/'
- found 'core' (0/5)
or
http://pb2.norway.sun.com/web.py?template=mysql_show_test_failure&test_failure_id=2295
mysql-trunk-build
508577 binary-max-sol10-sparc64-tar-gz
508623 takk-z5 test-max-sol10-sparc64
508745 tor04-z4 rpl_binlog_row binlog binlog_multi_engine None 2009-08-30 01:28:42
- Show/hide test output -
Original output
binlog.binlog_multi_engine w1 [ fail ]
Test ended at 2009-08-30 03:56:34
CURRENT_TEST: binlog.binlog_multi_engine
Start of 'mysql_cluster.1' cluster failed
- saving '/export/home/pb2/test/sb_0-719151-1251592045.55/mysql-5.4.3-beta-solaris10-sparc-test/mysql-test/var-rpl_binlog_row/1/log/binlog.binlog_multi_engine/' to '/export/home/pb2/test/sb_0-719151-1251592045.55/mysql-5.4.3-beta-solaris10-sparc-test/mysql-test/var-rpl_binlog_row/log/binlog.binlog_multi_engine/'
Retrying test, attempt(2/3)...
[3 Oct 2009 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
