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

innodb.innodb_max_recordsize_64k failed in buildbot with wrong result

    XMLWordPrintable

    Details

      Description

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

      innodb.innodb_max_recordsize_64k 'xtradb' w3 [ fail ]
              Test ended at 2018-02-03 14:09:55
       
      CURRENT_TEST: innodb.innodb_max_recordsize_64k
      --- /mnt/buildbot/build/mariadb-10.1.31/mysql-test/suite/innodb/r/innodb_max_recordsize_64k.result	2018-02-03 11:41:55.000000000 +0200
      +++ /mnt/buildbot/build/mariadb-10.1.31/mysql-test/suite/innodb/r/innodb_max_recordsize_64k.reject	2018-02-03 14:09:55.000000000 +0200
      @@ -539,10 +539,10 @@
       test.t	analyze	status	OK
       SELECT stat_value FROM mysql.innodb_index_stats where database_name = 'test' and table_name= 't' and stat_name='n_leaf_pages';
       stat_value
      -4
      +2
       SELECT clustered_index_size from mysql.innodb_table_stats where database_name = 'test' and table_name= 't';
       clustered_index_size
      -5
      +3
       DROP TABLE t;
       CREATE TABLE t(col BLOB) ENGINE=InnoDB ROW_FORMAT=REDUNDANT;
       SHOW WARNINGS;
       
      mysqltest: Result content mismatch
      

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              marko Marko Mäkelä
              Reporter:
              elenst Elena Stepanova
              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.