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

[10.1] encryption.innodb_lotoftables failed in buildbot with wrong result

    XMLWordPrintable

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest-big/builds/1766

      encryption.innodb_lotoftables 'innodb_plugin' w2 [ fail ]
              Test ended at 2018-04-30 17:01:01
       
      CURRENT_TEST: encryption.innodb_lotoftables
      --- /mnt/buildbot/build/mariadb-10.1.33/mysql-test/suite/encryption/r/innodb_lotoftables.result	2018-04-30 06:00:11.000000000 -0400
      +++ /mnt/buildbot/build/mariadb-10.1.33/mysql-test/suite/encryption/r/innodb_lotoftables.reject	2018-04-30 17:01:00.845259421 -0400
      @@ -923,6 +923,7 @@
       innodb_encrypted_3/t_99
       SELECT NAME FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION WHERE MIN_KEY_VERSION <> 0 AND NAME LIKE 'innodb_encrypted%' ORDER BY NAME;
       NAME
      +innodb_encrypted_1/t_68
       innodb_encrypted_2/t_1
       innodb_encrypted_2/t_10
       innodb_encrypted_2/t_100
      @@ -1129,6 +1130,7 @@
       innodb_encrypted_2/t_99
       SELECT NAME FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION WHERE MIN_KEY_VERSION = 0 AND NAME LIKE 'innodb_encrypted%' ORDER BY NAME;
       NAME
      +innodb_encrypted_1/t_68
       innodb_encrypted_3/t_1
       innodb_encrypted_3/t_10
       innodb_encrypted_3/t_100
       
      mysqltest: Result length mismatch
      

      Apparently it was fixed in 10.2 in the scope of MDEV-11531, but 10.1 is still affected.

      Attachments

        Issue Links

          Activity

            People

              marko Marko Mäkelä
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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