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

innodb.innodb_stats_persistent failed in buildbot with wrong result

    XMLWordPrintable

Details

    Description

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

      10.3 573c4db57a9b9fc5998bd2a2f1311873

      innodb.innodb_stats_persistent 'innodb'  w2 [ fail ]
              Test ended at 2018-11-13 22:28:21
       
      CURRENT_TEST: innodb.innodb_stats_persistent
      --- /mnt/buildbot/build/mariadb-10.3.11/mysql-test/suite/innodb/r/innodb_stats_persistent.result	2018-11-13 07:59:56.000000000 -0500
      +++ /mnt/buildbot/build/mariadb-10.3.11/mysql-test/suite/innodb/r/innodb_stats_persistent.reject	2018-11-13 22:28:20.782762345 -0500
      @@ -67,7 +67,7 @@
       1	SIMPLE	t2	ref	val	val	4	const	1	Using index
       SET @saved_frequency = @@GLOBAL.innodb_purge_rseg_truncate_frequency;
       SET GLOBAL innodb_purge_rseg_truncate_frequency = 1;
      -InnoDB		0 transactions not purged
      +InnoDB		30 transactions not purged
       SET GLOBAL innodb_purge_rseg_truncate_frequency = @saved_frequency;
       # After COMMIT and purge, the DELETE must show up.
       EXPLAIN SELECT * FROM t1 WHERE val=4;
       
      mysqltest: Result length mismatch
      

      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.