Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-13626 Merge InnoDB test cases from MySQL 5.7
  3. MDEV-14403

Review and fix tests from innodb_fts, innodb_zip, innodb_undo suites, merged from mysql 5.7

    XMLWordPrintable

    Details

    • Type: Technical task
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.2
    • Fix Version/s: 10.2
    • Component/s: Tests
    • Labels:
      None

      Description

      please review tests https://github.com/MariaDB/server/tree/bb-10.2-alice/mysql-test/suite/

      INNODB_UNDO suite

      -please check if results are correct in tests truncate and truncate_recover. (mysql results are in /r/ .result_mysql)
      -test undo_space_id has to be rewritten, it fails, so I disabled it for now.
      (mysqldump_max_recordsize.test and innodb_buffer_pool_load.test from innodb suite need to be rewritten in the same way (NEW_CMD), maybe correct them all at once)

      INNODB_ZIP

      tests that fail:

      prefix_index_liftedlimit : MDEV-14238
      wl6560 : --need to be rewritten l.184
      wl6470_1 : MDEV-14240
      wl6501 : fix

       
      innodb_zip.wl6501 '16k,innodb'           [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-11-15 12:41:30
      line
      2017-11-15 12:41:30 140477646644992 [ERROR] Table test/t1 has a primary key in InnoDB data dictionary, but not in MariaDB! Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html
      2017-11-15 12:41:30 140477646644992 [ERROR] InnoDB: Table test/t1 contains 1 indexes inside InnoDB, which is different from the number of indexes 0 defined in the MariaDB  Have you mixed up .frm files from different installations? See http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html
      2017-11-15 12:41:30 140477646644992 [ERROR] InnoDB: Table `test`.`t1` is corrupt.
      2017-11-15 12:41:30 140477646644992 [ERROR] mysqld: Table 't1' is marked as crashed and should be repaired
      ^ Found warnings in /home/alice/aliska/bb-10.2-alice/mysql-test/var/log/mysqld.1.err
      ok
       
       - saving '/home/alice/aliska/bb-10.2-alice/mysql-test/var/log/innodb_zip.wl6501-16k,innodb/' to '/home/alice/aliska/bb-10.2-alice/mysql-test/var/log/innodb_zip.wl6501-16k,innodb/'
      
      

      INNODB_FTS

      index_table : MDEV-14232
      limit_union : MDEV-14252
      sync : --comment in MDEV-13626
      opt : --comment MDEV-13626
      innobase_drop_fts_index_table : MDEV-14261
      phrase : — the same as in sync --comment in MDEV-13626
      compatibility : MDEV-14258
      fulltext3 : --test skip, require have_gb18030
      fulltext2 : – MDEV-14230
      plugin_debug : MDEV-14231

        Attachments

          Activity

            People

            Assignee:
            marko Marko Mäkelä
            Reporter:
            alice Alice Sherepa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.