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

innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do

    Details

    • Sprint:
      10.2.4-1, 10.2.4-2

      Description

      http://buildbot.askmonty.org/buildbot/builders/p8-rhel7-bintar-debug/builds/2018/steps/test/logs/stdio

      innodb.innodb_bug14676111 'innodb_plugin' w1 [ fail ]
              Test ended at 2017-01-05 22:06:59
       
      CURRENT_TEST: innodb.innodb_bug14676111
      --- /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/suite/innodb/r/innodb_bug14676111.result	2017-01-05 19:54:53.473261302 -0500
      +++ /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/suite/innodb/r/innodb_bug14676111.reject	2017-01-05 22:06:58.634010067 -0500
      @@ -22,7 +22,7 @@
       test.t1	analyze	status	OK
       select CLUST_INDEX_SIZE from information_schema.INNODB_SYS_TABLESTATS where NAME = 'test/t1';
       CLUST_INDEX_SIZE
      -8
      +10
       delete from t1 where a=5;
       set global innodb_purge_stop_now=ON;
       set global innodb_purge_run_now=ON;
       
      mysqltest: Result length mismatch
      

      Started happening quite regularly in buildbot on 10.1 tree since January 5, 2017.
      Observed on win32-debug, winx64-debug, p8-rhel7-bintar-debug.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                marko Marko Mäkelä
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: