Bug #34454 Some test cases from the 'rpl_ndb' suite fail
Submitted: 11 Feb 2008 11:17 Modified: 26 Mar 2008 16:34
Reporter: Alexander Nozdrin Email Updates:
Status: No Feedback
Category:Server: Tests Severity:S1 (Critical)
Version:5.1 OS:Any
Assigned to: Target Version:
Triage: D3 (Medium)

[11 Feb 2008 11:17] Alexander Nozdrin
Description:
The following test cases fail:
- rpl_ndb.rpl_ndb_innodb_trans
 
https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl_ndb.rpl_ndb_innodb_trans

- rpl_ndb.rpl_ndb_charset
  https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl_ndb.rpl_ndb_charset

- rpl_ndb.rpl_ndb_multi
  https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl_ndb.rpl_ndb_multi

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl_ndb.rpl_ndb_innodb_trans
https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl_ndb.rpl_ndb_charset
https://intranet.mysql.com/secure/pushbuild/xref.pl?testname=rpl_ndb.rpl_ndb_multi
[11 Feb 2008 11:24] Magnus Blaudd
When mysqld starts up it will connect to the cluster and create some system tables, until
those system tables are created(and events have been set up on those tables), the mysqld
will be in "read only" mode. I.e you can only open a table readonly. There is a loop in
the test script that is supposed to wai until mysqd has come out of the read only mode by
trying to open a table and then insert into it.
[11 Feb 2008 16:24] Bugs System
Pushed into 5.1.24-rc
[11 Feb 2008 16:26] Bugs System
Pushed into 6.0.5-alpha
[26 Feb 2008 16:34] Alexander Nozdrin
Looks as if these sporadic were fixed.
Set to "Need Feedback" -- if there is no failure anymore, this bug report
will be closed.
[27 Mar 2008 0: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".