[MDEV-4232] Galera: percona.innodb_sys_index fails due to a wrong version_comment (again) Created: 2013-03-03  Updated: 2013-03-03  Resolved: 2013-03-03

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.28a-galera
Fix Version/s: 5.5.29-galera

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Elena Stepanova
Resolution: Fixed Votes: 0
Labels: galera

Issue Links:
Relates

 Description   

percona.innodb_sys_index 'xtradb'        w2 [ fail ]
        Test ended at 2013-03-02 12:53:01
 
CURRENT_TEST: percona.innodb_sys_index
--- /mnt/buildbot/build/mariadb-5.5.29/mysql-test/suite/percona/innodb_sys_index.result	2013-03-02 12:27:09.000000000 +0200
+++ /mnt/buildbot/build/mariadb-5.5.29/mysql-test/suite/percona/innodb_sys_index.reject	2013-03-02 12:53:01.000000000 +0200
@@ -3,7 +3,7 @@
 Note	1051	Unknown table 't1'
 select @@version_comment limit 1 ;
 @@version_comment
-Source distribution, wsrep_X.Y.rZ
+Source distribution, wsrep_23.7.3.rXXXX
 SELECT COUNT(*) FROM `information_schema`.`INNODB_SYS_INDEXES` ;
 CREATE TABLE test.t1 (  `a` SERIAL NOT NULL ,  `b` VARCHAR( 255 ) NOT NULL ,  INDEX ( `b` )  ) ENGINE = InnoDB ;
 SHOW TABLE STATUS FROM `information_schema` LIKE 'INNODB\_SYS\_INDEXES%' ;

The version got the 3rd digit, which wasn't there before, and stopped matching the previous pattern.

I think it makes sense to generalize it even further.



 Comments   
Comment by Elena Stepanova [ 2013-03-03 ]

Pushed to maria-5.5-galera as revno 3388.

Generated at Thu Feb 08 06:54:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.