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

innodb_zip.restart fails in buildbot with wrong result

    XMLWordPrintable

Details

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

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-trusty-x86/builds/18469

      bb-10.5-release f35eeb791a130

      		 
      innodb_zip.restart '16k,crc32,innodb'    w1 [ fail ]
      		 
              Test ended at 2020-08-05 18:27:55
      		 
       
      		 
      CURRENT_TEST: innodb_zip.restart
      		 
      --- /usr/local/mariadb-10.5.5-linux-i686/mysql-test/suite/innodb_zip/r/restart.result	2020-08-05 17:15:41.000000000 +0000
      		 
      +++ /usr/local/mariadb-10.5.5-linux-i686/mysql-test/suite/innodb_zip/r/restart.reject	2020-08-05 18:27:55.049795974 +0000
      		 
      @@ -506,6 +506,7 @@
      		 
       t7_restart.frm
      		 
       t7_restart.par
      		 
       ---- MYSQL_TMP_DIR/alt_dir/test
      		 
      +#sql-ib30.ibd
      		 
       t5_restart.ibd
      		 
       t5_restart.ibd.bak
      		 
       t6_restart#p#p0.ibd
      		 
       
      		 
      mysqltest: Result length mismatch

      Attachments

        Issue Links

          is caused by

          Task - A task that needs to be done. MDEV-16678 Use MDL for innodb background threads instead of dict_operation_lock

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          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.