Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-25947

innodb_fts.misc_debug fails in buildbot

    XMLWordPrintable

    Details

      Description

      The test case fails in the buildbot:
      http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/6627/steps/mtr/logs/stdio

       
      CURRENT_TEST: innodb_fts.misc_debug
      --- /usr/share/mysql-test/suite/innodb_fts/r/misc_debug.result	2021-06-15 16:40:45.000000000 +0000
      +++ /dev/shm/var/3/log/misc_debug.reject	2021-06-15 18:42:59.119142408 +0000
      @@ -39,6 +39,8 @@
       SET DEBUG_SYNC='now WAIT_FOR s1';
       KILL QUERY @id;
       SET DEBUG_SYNC='now SIGNAL g1 WAIT_FOR s2';
      +Warnings:
      +Warning	1639	debug sync point wait timed out
       START TRANSACTION;
       SELECT * FROM t1;
       a	b	c
       
      mysqltest: Result length mismatch
      
      

      I can able to repeat the issue locally. I don't see any failure inside InnoDB.
      To make the test case more stable. I would like to do the change the
      test case of MDEV-25200. Tested the changes in 10.2.37 and
      confirmed that it repeats the issue.

      #
      # MDEV-25200 Index count mismatch due to aborted FULLTEXT INDEX
      #
      CREATE TABLE t1(a INT, b TEXT, c TEXT, FULLTEXT INDEX(b)) ENGINE=InnoDB;
      connect con1,localhost,root,,test;
      SET DEBUG_DBUG="+d,innodb_OOM_inplace_alter";
      SET DEBUG_SYNC='innodb_commit_inplace_alter_table_enter SIGNAL s2 WAIT_FOR g2';
      ALTER TABLE t1 ADD FULLTEXT(c);
      connection default;
      SET DEBUG_SYNC='now WAIT_FOR s2';
      START TRANSACTION;
      SELECT * FROM t1;
      a	b	c
      SET DEBUG_SYNC='now SIGNAL g2';
      connection con1;
      ERROR HY000: Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
      disconnect con1;
      connection default;
      SET DEBUG_SYNC=RESET;
      ALTER TABLE t1 ADD bl INT AS (LENGTH(b)) VIRTUAL;
      Warnings:
      Warning	1082	InnoDB: Table test/t1 contains 2 indexes inside InnoDB, which is different from the number of indexes 1 defined in the MariaDB 
      CHECK TABLE t1;
      Table	Op	Msg_type	Msg_text
      test.t1	check	status	OK
      DROP TABLE t1;
      innodb_fts.f3 'innodb'                   [ fail ]  Found warnings/errors in server log file!
              Test ended at 2021-06-17 15:26:28
      line
      2021-06-17 15:26:28 139763778254592 [ERROR] InnoDB: Table test/t1 contains 2 indexes inside InnoDB, which is different from the number of indexes 1 defined in the MariaDB  Have you mixed up .frm files from different installations? See https://mariadb.com/kb/en/innodb-troubleshooting/
      ^ Found warnings in /home/thiru/mariarepo/10.2/10.2-sample/bld_sample-debug/mysql-test/var/log/mysqld.1.err
      
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              thiru Thirunarayanan Balathandayuthapani
              Reporter:
              thiru Thirunarayanan Balathandayuthapani
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration