mtr tests for cluster node
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership | Status tracked in 5.6 | |||||
5.5 |
Won't Fix
|
Wishlist
|
Unassigned | |||
5.6 |
Fix Released
|
Wishlist
|
Unassigned | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Won't Fix
|
Wishlist
|
Unassigned | |||
5.6 |
Fix Committed
|
Wishlist
|
Unassigned |
Bug Description
This bug will be used as a tracker for all the development that is needed for enabling the testing of single wsrep node cluster with mysql test run (mtr) framework.
There is a sibling bug: lp:856162, for which the goal is to make sure that mtr testing for wsrep node, with no wsrep_provider, will be successful. Whereas, In this bug, we are testing node with wsrep_provider functionality.
Following sub tasks should be worked on:
* figure out and document a suitable way for mtr to launch wsrep nodes
* find out which mtr tests pass, and which cannot be supported
For non supported tests:
* document the reason why they must be skipped
* maintain a list of non-supported tests, so that they can be skipped by mtr
* some tests, that should pass, will show errors, work on these case by case
Changed in codership-mysql: | |
status: | New → In Progress |
importance: | Undecided → Wishlist |
innodb/innodb test for a debug build wsrep node failed for a debug assert in handler.cc:
in wsrep_innobase_ mysql_sort( ) ASSERT( tmp_length <= str_length);
...
DBUG_
This assert is too strong, fix was pushed in wsrep-5.6, in revision: bazaar. launchpad. net/~codership/ codership- mysql/5. 6/revision/ 4034
http://