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

innodb.purge_secondary fails in buildbot with wrong result

    XMLWordPrintable

Details

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

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/12052/steps/mtr_nm/logs/stdio

      innodb.purge_secondary 'innodb'          w3 [ fail ]
              Test ended at 2018-03-26 15:26:19
       
      CURRENT_TEST: innodb.purge_secondary
      --- /mnt/buildbot/build/mariadb-10.2.14/mysql-test/suite/innodb/r/purge_secondary.result	2018-03-26 13:44:58.000000000 +0300
      +++ /mnt/buildbot/build/mariadb-10.2.14/mysql-test/suite/innodb/r/purge_secondary.reject	2018-03-26 15:26:19.000000000 +0300
      @@ -158,7 +158,6 @@
       SELECT NAME, SUBSYSTEM FROM INFORMATION_SCHEMA.INNODB_METRICS
       WHERE NAME="buffer_LRU_batch_evict_total_pages" AND COUNT > 0;
       NAME	SUBSYSTEM
      -buffer_LRU_batch_evict_total_pages	buffer
       # Note: The OTHER_INDEX_SIZE does not cover any SPATIAL INDEX.
       # To test that all indexes were emptied, replace DROP TABLE
       # with the following, and examine the root pages in t1.ibd:
       
      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.