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

encryption.innodb-first-page-read fails in buildbot with timeout on wait condition

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.1
    • N/A
    • Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/10333/steps/test_2/logs/stdio

      encryption.innodb-first-page-read 'cbc,innodb_plugin' w4 [ fail ]
              Test ended at 2017-11-09 17:13:24
       
      CURRENT_TEST: encryption.innodb-first-page-read
      --- /mnt/buildbot/build/mariadb-10.1.29/mysql-test/suite/encryption/r/innodb-first-page-read.result	2017-11-09 14:44:45.000000000 +0200
      +++ /mnt/buildbot/build/mariadb-10.1.29/mysql-test/suite/encryption/r/innodb-first-page-read.reject	2017-11-09 17:13:23.000000000 +0200
      @@ -68,6 +68,9 @@
       1
       set global innodb_encrypt_tables=OFF;
       # wait until tables are decrypted
      +Timeout in wait_condition.inc for SELECT COUNT(*) = 0 FROM INFORMATION_SCHEMA.INNODB_TABLESPACES_ENCRYPTION WHERE MIN_KEY_VERSION <> 0
      +Id	User	Host	db	Command	Time	State	Info	Progress
      +2	root	localhost	test	Query	0	init	show full processlist	0.000
       # result should be actual number of tables except remote tables could be read twice
       # i.e. < 23 + 3*2 = 29
       SELECT VARIABLE_VALUE <= 29  FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'innodb_pages0_read';
       
      mysqltest: Result length mismatch
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            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.