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

innodb.truncate_purge_debug fails sporadically in buildbot

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.2.6
    • 10.2.6
    • Tests
    • None

    Description

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

      innodb.truncate_purge_debug 'innodb'     w1 [ fail ]
      		 
              Test ended at 2017-05-03 11:08:13
      		 
       
      		 
      CURRENT_TEST: innodb.truncate_purge_debug
      		 
      --- /mnt/buildbot/build/mariadb-10.2.6/mysql-test/suite/innodb/r/truncate_purge_debug.result	2017-05-03 09:30:39.000000000 +0300
      		 
      +++ /mnt/buildbot/build/mariadb-10.2.6/mysql-test/suite/innodb/r/truncate_purge_debug.reject	2017-05-03 11:08:12.000000000 +0300
      		 
      @@ -24,6 +24,8 @@
      		 
       SET DEBUG_SYNC = 'now SIGNAL finish_scan';
      		 
       SET DEBUG_SYNC = 'RESET';
      		 
       connection con1;
      		 
      +Warnings:
      		 
      +Warning	1639	debug sync point wait timed out
      		 
       disconnect con1;
      		 
       connection default;
      		 
       drop table t1;
      		 
       
      		 
      mysqltest: Result length mismatch

      Attachments

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11802 innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-12754 innodb.truncate_debug fails in buildbot with embedded due to semaphore wait

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-11802 innodb.innodb_bug14676111 fails in buildbot due to InnoDB purge failing to start when there is work to do

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova created issue -
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            Status Open [ 1 ] Confirmed [ 10101 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä added a comment -

            This sporadic failure ("debug sync point wait timed out") is a duplicate of MDEV-12754.

            There is another (independent) sporadic failure that should be tracked and fixed under this ticket (it looks like MDEV-11802 might not be fully fixed):

            CURRENT_TEST: innodb.truncate_purge_debug
            		 
            --- /mariadb/10.2/mysql-test/suite/innodb/r/truncate_purge_debug.result	2017-04-26 23:03:32.060878489 +0300
            		 
            +++ /mariadb/10.2/mysql-test/suite/innodb/r/truncate_purge_debug.reject	2017-05-10 11:01:43.462853528 +0300
            		 
            @@ -19,7 +19,7 @@
            		 
             COMMIT;
            		 
             disconnect con2;
            		 
             connection default;
            		 
            -InnoDB		0 transactions not purged
            		 
            +InnoDB		1 transactions not purged
            		 
             SET GLOBAL innodb_purge_rseg_truncate_frequency = @saved_frequency;
            		 
             SET DEBUG_SYNC = 'now SIGNAL finish_scan';
            		 
             SET DEBUG_SYNC = 'RESET';
            		 
             
            		 
            mysqltest: Result content mismatch

            marko Marko Mäkelä added a comment - This sporadic failure ("debug sync point wait timed out") is a duplicate of MDEV-12754 . There is another (independent) sporadic failure that should be tracked and fixed under this ticket (it looks like MDEV-11802 might not be fully fixed): CURRENT_TEST: innodb.truncate_purge_debug --- /mariadb/10.2/mysql-test/suite/innodb/r/truncate_purge_debug.result 2017-04-26 23:03:32.060878489 +0300 +++ /mariadb/10.2/mysql-test/suite/innodb/r/truncate_purge_debug.reject 2017-05-10 11:01:43.462853528 +0300 @@ -19,7 +19,7 @@ COMMIT; disconnect con2; connection default; -InnoDB 0 transactions not purged +InnoDB 1 transactions not purged SET GLOBAL innodb_purge_rseg_truncate_frequency = @saved_frequency; SET DEBUG_SYNC = 'now SIGNAL finish_scan'; SET DEBUG_SYNC = 'RESET';   mysqltest: Result content mismatch
            marko Marko Mäkelä made changes -
            Status Confirmed [ 10101 ] In Progress [ 3 ]
            marko Marko Mäkelä made changes -
            Affects Version/s 10.2.6 [ 22527 ]
            Affects Version/s 10.2 [ 14601 ]
            marko Marko Mäkelä added a comment -

            I pushed a workaround that wakes up the purge when SHOW ENGINE INNODB STATUS is executed. That is what the test innodb.truncate_purge_debug uses for polling.

            Note: the test will often still fail due to the lost DEBUG_SYNC signal (MDEV-12754).

            marko Marko Mäkelä added a comment - I pushed a workaround that wakes up the purge when SHOW ENGINE INNODB STATUS is executed. That is what the test innodb.truncate_purge_debug uses for polling. Note: the test will often still fail due to the lost DEBUG_SYNC signal ( MDEV-12754 ).
            marko Marko Mäkelä made changes -
            issue.field.resolutiondate 2017-05-10 11:38:51.0 2017-05-10 11:38:51.851
            marko Marko Mäkelä made changes -
            Fix Version/s 10.2.6 [ 22527 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            marko Marko Mäkelä made changes -
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 80629 ] MariaDB v4 [ 152102 ]

            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.